|
|
| (9 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | == Requirements ==
| + | <big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer3:Launcher here]</font></big> |
| − | | |
| − | [[2007_Project_Half_Week#Projects | One of the projects]] at the 2007 AHM was a [[2007_AHM_Programming_Half_Week_Slicer3_Launch.ppt | review of the Slicer3 launcher]].
| |
| − | | |
| − | A summary of the conculusions is:
| |
| − | * for the shared library plugins to work the application needs to be built in shared mode (not static)
| |
| − | * this means that shared library paths must be set ''before'' the application is started
| |
| − | * a launcher can do this -- it is a small program that does not have shared library dependencies that sets paths and then executes the main application
| |
| − | | |
| − | Some other nice things the launcher can do:
| |
| − | * since the launcher starts quickly, it can put up a splash screen for user feedback while the main program is loading
| |
| − | * the launcher can catch abnormal termination conditions of the main program and provide user feedback
| |
| − | | |
| − | == Implementation ==
| |
| − | | |
| − | The group decided to adopt the approach used by slicer2, which is based on the [http://www.equi4.com/starkit.html starkit/starpack] technology for building small, stand alone programs that include a full tcl/tk interpreter. | |
| − | | |
| − | The code and documentation are in Slicer3/Utilities/Launcher. The actual startup script is Slicer3/launch.tcl.in, which gets configured by cmake into Slicer3-build/lib/launch.tcl.
| |
Latest revision as of 17:59, 10 July 2017
Home < Slicer3:LauncherNote: We are migrating this content to the slicer.org domain - The newer page is here
