Documentation/4.0/Developers/Tutorials/QtDesigner - Revision history

UpdateBot: Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-06-14T07:29:55Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

Finetjul: /* = Windows notes */

2012-03-02T03:42:42Z

= Windows notes

Finetjul at 03:42, 2 March 2012

2012-03-02T03:42:13Z

Finetjul: /* Build Slicer */

2012-03-02T03:41:28Z

Build Slicer

Finetjul: /* Running Qt Designer with the correct environment variables */

2012-03-02T03:41:11Z

Running Qt Designer with the correct environment variables

Finetjul: /* Running Qt Designer with the correct environment variables */

2012-03-02T03:40:33Z

Running Qt Designer with the correct environment variables

Kikinis at 15:25, 21 November 2011

2011-11-21T15:25:31Z

JChris.FillionR at 03:23, 2 November 2011

2011-11-02T03:23:55Z

JChris.FillionR: moved Slicer4:Developers:Projects:QtSlicer/Tutorials/QtDesigner to Documentation/4.0/Developers/Tutorials/QtDesigner

2011-11-02T03:20:05Z

moved Slicer4:Developers:Projects:QtSlicer/Tutorials/QtDesigner to Documentation/4.0/Developers/Tutorials/QtDesigner

Finetjul at 19:25, 19 January 2011

2011-01-19T19:25:31Z

← Older revision		Revision as of 07:29, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	Back to [[Documentation/{{documentation/version}}/Developers\|Developers Information]]←		Back to [[Documentation/{{documentation/version}}/Developers\|Developers Information]]←

@@ Line 16: / Line 16: @@
 *the second is to set the environment variable <code>QT_PLUGIN_PATH</code> to the directory <i>Slicer-build/bin</i> containing the subdirectory <i>designer</i> with the plugin libraries.<br>
 '''Note:''' Qt requires that the directory containing the designer plugins is named "designer".<br>
-=== Windows notes ==
+=== Windows notes ===
 On Windows, Qt Designer can only load plugins that have been compiled in the same build mode than Qt Designer. For example, if Qt is built in Debug mode, the plugins must also be built in Debug mode to be loaded by Qt Designer.<br>
 If Qt is configured to build in both debug and release modes, Qt Designer is built in release mode only. If that case, it is necessary to ensure that plugins are also built in release mode. Otherwise, you can open the solution file for Qt, and recompile Designer in debug mode.

@@ Line 8: / Line 8: @@
 <pre>
 cd Slicer-build;
-Slicer4 --designer
+./Slicer --designer
 </pre>
@@ Line 30: / Line 30: @@
 |colspan="2"|
   $ cd Slicer-build
-  $ ./Slicer4 --designer
+  $ ./Slicer --designer
+|
   > cd Slicer-build
-  > .\Slicer4.exe --designer
+  > .\Slicer.exe --designer
 |}
 {|

@@ Line 61: / Line 61: @@
 |-
 |colspan="2"|<pre>$ ./Slicer</pre>
-| <pre>.\Slicer.exe</pre>
+| <pre>> .\Slicer.exe</pre>
 |}

@@ Line 32: / Line 32: @@
   $ ./Slicer4 --designer
+|
-  $ cd Slicer-build
+  > cd Slicer-build
-  $ .\Slicer4.exe --designer
+  > .\Slicer4.exe --designer
 |}
 {|
 |[[Image:Screenshot-Qt Designer.png|thumb|300px|Qt Desginer loaded with CTKWidgets and qMRMLWidgets]]
 |}
 ==Build Slicer==
 * Once you are satisfied with UI, save the file, quit Designer and build Slicer to take the changes into account.

@@ Line 23: / Line 23: @@
 *On Windows, compile Slicer in the same build mode than Qt. If Qt is in Debug mode, compile Slicer in Debug mode, if it's in Release or Debug&Release mode, compile Slicer in Release mode.
 *run Qt Designer via Slicer launcher located in <i>Slicer-build</i>.
-<pre>
+{| style="border: 1px solid darkgray;"
-cd Slicer-build;
+!align=left style="border-bottom: 1px solid grey;"|Mac Os X
-Slicer4 --designer
+!align=left style="border-bottom: 1px solid grey;"|Linux
-</pre>
+!align=left style="border-bottom: 1px solid grey;"|Windows
-'''Note:''' <i>Designer.py</i> scripts are not supported anymore.
+|-
 {|
 |[[Image:Screenshot-Qt Designer.png|thumb|300px|Qt Desginer loaded with CTKWidgets and qMRMLWidgets]]
 |}

@@ Line 1: / Line 1: @@
-[[Documentation/{{documentation/version}}/Developers|Tutorials]]&larr;
+Back to [[Documentation/{{documentation/version}}/Developers|Developers Information]]&larr;
 =Using custom widgets in Qt Designer=
 ==Straight to the point==

← Older revision	Revision as of 03:20, 2 November 2011
(No difference)

@@ Line 3: / Line 3: @@
 ==Straight to the point==
 *Windows
-**Compile Slicer in Release mode
+**Compile Slicer in Release mode OR build Qt in Debug
-**Double clic on <i>Designer-Release.py</i> located in <i>Slicer3-build</i>
+*All
 <pre>
 cd Slicer-build;
@@ Line 12: / Line 11: @@
 ==Qt Designer requirements==
-In order to have the CTK and MRML widgets in Qt Designer, Qt Designer offers 2 options. The first (not detailed here) is to copy (or symlink) the CTK and MRML plugin libraries into <i>%QT_DIR%/plugins/designer</i>, the second is to set the environment variable <code>QT_PLUGIN_PATH</code> to the directory <i>Slicer3-build/bin</i> containing the subdirectory <i>designer</i> with the plugin libraries.<br>
+In order to have the CTK and MRML widgets in Qt Designer, Qt Designer offers 2 options:
 '''Note:''' Qt requires that the directory containing the designer plugins is named "designer".<br>
-Moreover, Qt Designer can only load plugins that have been compiled in the same build mode than Qt Designer. For example, if Qt is built in Debug mode, the plugins must also be built in Debug mode to be loaded by Qt Designer.<br>
+=== Windows notes ==
-'''Note:''' If Qt is configured to build in both debug and release modes, Qt Designer is built in release mode only. If that case, it is necessary to ensure that plugins are also built in release mode.
+On Windows, Qt Designer can only load plugins that have been compiled in the same build mode than Qt Designer. For example, if Qt is built in Debug mode, the plugins must also be built in Debug mode to be loaded by Qt Designer.<br>
 ==Running Qt Designer with the correct environment variables==
-*Compile Slicer in the same build mode than Qt. If Qt is in Debug mode, compile Slicer in Debug mode, if it's in Release or Debug&Release mode, compile Slicer in Release mode.
+*On Windows, compile Slicer in the same build mode than Qt. If Qt is in Debug mode, compile Slicer in Debug mode, if it's in Release or Debug&Release mode, compile Slicer in Release mode.
 *run Qt Designer via Slicer launcher located in <i>Slicer-build</i>.
 <pre>
@@ Line 24: / Line 26: @@
 Slicer4 --designer
 </pre>
-'''Note:''' For MS Visual Studio users, there is a <i>Designer</i> python script for each build mode. Execute the script according to the build mode.
+'''Note:''' <i>Designer.py</i> scripts are not supported anymore.
 {|
 |[[Image:Screenshot-Qt Designer.png|thumb|300px|Qt Desginer loaded with CTKWidgets and qMRMLWidgets]]
 |}