Documentation/Labs/CustomSlicerGenerator - Revision history

Pieper: /* As of March 6, 2015 */

2015-03-06T19:08:27Z

As of March 6, 2015

Pieper: /* As of March 6, 2015 */

2015-03-06T19:00:44Z

As of March 6, 2015

Pieper: /* Implementation Progress */

2015-03-06T16:07:23Z

Implementation Progress

Pieper: /* Implementation Progress */

2015-02-23T01:15:57Z

Implementation Progress

Pieper: /* Implementation Progress */

2015-02-23T01:12:49Z

Implementation Progress

Pieper: /* Implementation Progress */

2015-02-22T21:25:23Z

Implementation Progress

Pieper: /* Implementation Progress */

2015-02-22T21:10:13Z

Implementation Progress

Pieper: /* Implementation Progress */

2015-02-22T21:09:50Z

Implementation Progress

Pieper: /* Implementation Progress */

2015-02-22T21:09:34Z

Implementation Progress

Pieper: /* Issues to sort out */

2015-02-22T21:04:39Z

Issues to sort out

@@ Line 68: / Line 68: @@
 *** configure the logos
 *** figures out how to set Extension paths correctly and prompts for restart
 * TODO items

@@ Line 67: / Line 67: @@
 *** create a custom layout or other interface
 *** configure the logos
 * TODO items
 ** add automatic zip file creation with date and platform information
 ** maybe uploading zip to a server
 ** see if Customizer can auto-load extension modules without requring a reboot
 ** testing on all platforms
 ** fetching the config.json file from a url rather than on-disk (so it can come from a controlled repository)
 ** Communicating with other project for other requirements (SlicerRT, SlicerIGT, SlicerRadiomics, SlicerProstate...)

@@ Line 43: / Line 43: @@
 A new extension has been created: https://github.com/pieper/CustomSlicerGenerator
-As of late February 2015 it mostly works and creates a custom application with the modules specified by a configuration script.  The resulting custom application runs, but it uses the settings from Slicer because the application name is [https://github.com/Slicer/Slicer/blob/9ab851e646f7eb755d27e0fb9d367d97ee55ad08/Applications/SlicerApp/Main.cxx#L108 hard-coded in Slicer's Main.cxx].
+===As of late February 2015===
@@ Line 53: / Line 54: @@
 It will also be important to save provenance about the custom slicer version to help with support and debugging.  Basically the custom app will be a whole new application so it needs it's own versioning.  Probably the config.json should come from a git repository (something like a .s4ext) so that the version can be generated from that.  Then in the future this process can be automated and the git repository info about the config file will uniquely define the custom slicer that was generated and therefor all the dependencies can be traced back as well.

← Older revision		Revision as of 01:15, 23 February 2015
Line 51:		Line 51:

	We also need to update the Info.plist for mac and the app launcher settings for windows and linux to point to the newly custom-named App-real executable.		We also need to update the Info.plist for mac and the app launcher settings for windows and linux to point to the newly custom-named App-real executable.
		+
		+	It will also be important to save provenance about the custom slicer version to help with support and debugging. Basically the custom app will be a whole new application so it needs it's own versioning. Probably the config.json should come from a git repository (something like a .s4ext) so that the version can be generated from that. Then in the future this process can be automated and the git repository info about the config file will uniquely define the custom slicer that was generated and therefor all the dependencies can be traced back as well.

← Older revision		Revision as of 01:12, 23 February 2015
Line 49:		Line 49:

	Since we are using the [http://www.commontk.org/index.php/Tools:_Application_launcher ctkApplicationLauncher], we will need to change the settings to point to SlicerCustomApp-real{.exe} and when processing argv0 we'll need to strip that off.		Since we are using the [http://www.commontk.org/index.php/Tools:_Application_launcher ctkApplicationLauncher], we will need to change the settings to point to SlicerCustomApp-real{.exe} and when processing argv0 we'll need to strip that off.
		+
		+	We also need to update the Info.plist for mac and the app launcher settings for windows and linux to point to the newly custom-named App-real executable.

← Older revision		Revision as of 21:25, 22 February 2015
Line 47:		Line 47:

	If the applicationName is not set, newer [https://qt.gitorious.org/qt/qtbase/source/6716fe8cfdeb5f8cd63d6dde8252b25d86622404:src/corelib/kernel/qcoreapplication.cpp#L154 Qt will use either argv or a mac-specific method to guess a name]. But this isn't really what we want since we use the launcher on linux and windows and we don't want to mess around modifying with the mac-specific stuff if it can be avoided. Note that the application name needs to be pretty much right away during the startup process. So we'll need to have a custom solution for this rather than porting over the new Qt code.		If the applicationName is not set, newer [https://qt.gitorious.org/qt/qtbase/source/6716fe8cfdeb5f8cd63d6dde8252b25d86622404:src/corelib/kernel/qcoreapplication.cpp#L154 Qt will use either argv or a mac-specific method to guess a name]. But this isn't really what we want since we use the launcher on linux and windows and we don't want to mess around modifying with the mac-specific stuff if it can be avoided. Note that the application name needs to be pretty much right away during the startup process. So we'll need to have a custom solution for this rather than porting over the new Qt code.
		+
		+	Since we are using the [http://www.commontk.org/index.php/Tools:_Application_launcher ctkApplicationLauncher], we will need to change the settings to point to SlicerCustomApp-real{.exe} and when processing argv0 we'll need to strip that off.

← Older revision		Revision as of 21:10, 22 February 2015
Line 46:		Line 46:


−	If the applicationName is not set, newer [https://qt.gitorious.org/qt/qtbase/source/6716fe8cfdeb5f8cd63d6dde8252b25d86622404:src/corelib/kernel/qcoreapplication.cpp#L154 Qt will use either argv~~\[0\]~~ or a mac-specific method to guess a name]. But this isn't really what we want since we use the launcher on linux and windows and we don't want to mess around modifying with the mac-specific stuff if it can be avoided. Note that the application name needs to be pretty much right away during the startup process. So we'll need to have a custom solution for this rather than porting over the new Qt code.	+	If the applicationName is not set, newer [https://qt.gitorious.org/qt/qtbase/source/6716fe8cfdeb5f8cd63d6dde8252b25d86622404:src/corelib/kernel/qcoreapplication.cpp#L154 Qt will use either argv or a mac-specific method to guess a name]. But this isn't really what we want since we use the launcher on linux and windows and we don't want to mess around modifying with the mac-specific stuff if it can be avoided. Note that the application name needs to be pretty much right away during the startup process. So we'll need to have a custom solution for this rather than porting over the new Qt code.

← Older revision		Revision as of 21:09, 22 February 2015
Line 46:		Line 46:


−	If the applicationName is not set, newer [https://qt.gitorious.org/qt/qtbase/source/6716fe8cfdeb5f8cd63d6dde8252b25d86622404:src/corelib/kernel/qcoreapplication.cpp#L154 Qt will use either argv[0] or a mac-specific method to guess a name]. But this isn't really what we want since we use the launcher on linux and windows and we don't want to mess around modifying with the mac-specific stuff if it can be avoided. Note that the application name needs to be pretty much right away during the startup process. So we'll need to have a custom solution for this rather than porting over the new Qt code.	+	If the applicationName is not set, newer [https://qt.gitorious.org/qt/qtbase/source/6716fe8cfdeb5f8cd63d6dde8252b25d86622404:src/corelib/kernel/qcoreapplication.cpp#L154 Qt will use either argv\[0\] or a mac-specific method to guess a name]. But this isn't really what we want since we use the launcher on linux and windows and we don't want to mess around modifying with the mac-specific stuff if it can be avoided. Note that the application name needs to be pretty much right away during the startup process. So we'll need to have a custom solution for this rather than porting over the new Qt code.

← Older revision		Revision as of 21:09, 22 February 2015
Line 44:		Line 44:

	As of late February 2015 it mostly works and creates a custom application with the modules specified by a configuration script. The resulting custom application runs, but it uses the settings from Slicer because the application name is [https://github.com/Slicer/Slicer/blob/9ab851e646f7eb755d27e0fb9d367d97ee55ad08/Applications/SlicerApp/Main.cxx#L108 hard-coded in Slicer's Main.cxx].		As of late February 2015 it mostly works and creates a custom application with the modules specified by a configuration script. The resulting custom application runs, but it uses the settings from Slicer because the application name is [https://github.com/Slicer/Slicer/blob/9ab851e646f7eb755d27e0fb9d367d97ee55ad08/Applications/SlicerApp/Main.cxx#L108 hard-coded in Slicer's Main.cxx].
		+
		+
		+	If the applicationName is not set, newer [https://qt.gitorious.org/qt/qtbase/source/6716fe8cfdeb5f8cd63d6dde8252b25d86622404:src/corelib/kernel/qcoreapplication.cpp#L154 Qt will use either argv[0] or a mac-specific method to guess a name]. But this isn't really what we want since we use the launcher on linux and windows and we don't want to mess around modifying with the mac-specific stuff if it can be avoided. Note that the application name needs to be pretty much right away during the startup process. So we'll need to have a custom solution for this rather than porting over the new Qt code.

← Older revision		Revision as of 21:04, 22 February 2015
Line 38:		Line 38:

	* How to remove module menu groups like "Diffusion" when they are empty.		* How to remove module menu groups like "Diffusion" when they are empty.
		+
		+	== Implementation Progress ==
		+
		+	A new extension has been created: https://github.com/pieper/CustomSlicerGenerator
		+
		+	As of late February 2015 it mostly works and creates a custom application with the modules specified by a configuration script. The resulting custom application runs, but it uses the settings from Slicer because the application name is [https://github.com/Slicer/Slicer/blob/9ab851e646f7eb755d27e0fb9d367d97ee55ad08/Applications/SlicerApp/Main.cxx#L108 hard-coded in Slicer's Main.cxx].