Difference between revisions of "2011 Winter Project Week: Python and Slicer4"

Revision as of 18:42, 9 January 2011

Home < 2011 Winter Project Week: Python and Slicer4

Develop scripting patterns for implementing workflows in slicer4 to port slicer3 functionality and streamline implementation of new functionality.

Review initial experiences with PythonQt in slicer4
- Editor and SWidgets
- TubeTK-based Interactive PDF Segmenter
- Endoscopy
Consider general architecture for creating module GUIs (scripted widgets)
- allow adaptive re-use of widgets in different modules such as:
  - embed subset of painting tools inside interactive segmenters
  - embed small model maker interface in segmentation tools
  - embed some annotation (e.g. fiducial) for landmarking in registration
  - embed CLI interfaces in workflow wizards
- define inheritance for PythonQt implementations to provide consistency across module GUI implementaitons
Consider use cases for (scripted) slicer modules - can one implementation pattern cover all use cases?
- embed GUI in slicer interface (parent is slicer module panel)
- run as part of a workflow (parent is one step of workflow)
- run GUI stand-alone (module's widget is top level window)
- run without GUI (parameters passed on command line CLI-style)

Slicer4 developer beta supports PythonQt scripted modules.

[image:LabelStatistics-Module-2011-01-09.png|thumb|300px|Label Statistics running as a slicer module].

@@ Line 48: / Line 48: @@
 </div>
-<!--<div style="width: 97%; float: left;">
+<div style="width: 97%; float: left;">
 ==References==
+Example [http://viewvc.slicer.org/viewcvs.cgi/trunk/QTScriptedModules/Scripts/LabelStatistics.py?rev=15801&root=Slicer4&view=markup LabelStatistics module source code].
+[image:LabelStatistics-Module-2011-01-09.png|thumb|300px|Label Statistics running as a slicer module].
 </div>
--->