Difference between revisions of "2010 Winter Project Week Qt-ing the Command Line Module"

From NAMIC Wiki
Jump to: navigation, search
Line 28: Line 28:
 
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.
 
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:
+
Porting the CommandLineModule to Qt involves:
 
* Automatic GUI generation using Qt in places of KWWidgets
 
* Automatic GUI generation using Qt in places of KWWidgets
 
* Populate GUI with values from MRML
 
* Populate GUI with values from MRML

Revision as of 14:59, 2 January 2010

Home < 2010 Winter Project Week Qt-ing the Command Line Module

Key Investigators

  • GE: Jim Miller
  • Kitware: Jean-Christophe Fillion-Robin, Julien Finet

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 involves:

  • 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