Difference between revisions of "2010 Winter Project Week Qt-ing the Command Line Module"
From NAMIC Wiki
Line 49: | Line 49: | ||
==References== | ==References== | ||
− | * | + | *[http://www.slicer.org/slicerWiki/index.php/Slicer3:Execution_Model_Documentation Execution Model Documentation] |
− | * | + | *[http://www.slicer.org/slicerWiki/index.php/Qt_in_Slicer3 Qt in Slicer3] |
− | * | + | *[http://wiki.slicer.org/slicerWiki/index.php/Slicer3:Developers:Projects:QtSlicer QtSlicer] |
− | * | + | *[http://qt.nokia.com/ Qt] |
− | |||
</div> | </div> |
Revision as of 14:58, 2 January 2010
Home < 2010 Winter Project Week Qt-ing the Command Line ModuleKey Investigators
- GE: Jim Miller
- Kitware: Juliens
Objective
Port the CommandLineModule infrastructure for automatic GUI construction to Qt.
Approach, Plan
The CommandLineModule uses a data specification in XML to define the inputs and outputs of a module. The module automatically constructs a user interface that interacts with the MRML scene using this data specification. Historically, the module has used KWWidgets and Slicer specific widgets for all user interface components.
Porting the CommandLineModule to Qt involve:
- Automatic GUI generation using Qt in places of KWWidgets
- Populate GUI with values from MRML
- Callback process to populate MRML from GUI
This port is already under way and we will use the week to refine and extend.
Progress