Projects:ARRA:SlicerEM Meeting 07082010

Back to SlicerEM:Developer page

Purpose

Kickoff meeting

Attendants

• Stephen Aylward
• Sebastien Barre
• Jean-Christophe Fillion-Robin
• Julien Finet
• Danielle Pace

Workflow Manager

Should be incorporated into CTK . There are two options:

• Option1: Keep VTK "stuff"
• Option2: just go ahead and convert to full Qt

Option2 is preferred: Sebastien has already some generic classes build over QtStateMachine framework that he could re-used.

UI within QtDesigner

• The discussed solution will consist in having a UI file with a stacked widget where each step would be layered in the stack.
• Optionnaly, complex step could be design using QtDesigner and saved in a dedicated UI File. The corresponding class could then been expored as QtDesigner pluing or promoted.

Wizzard

• Since the Wizzard classes bundled with Qt are not generic enough, designining our own Wizzard class will also be needed. Seb mentionned it shouldn't be difficult to re-design.
• The wizzard will implement a convenience layer to make sure a given state is completed before switching to the next step.
• Naming convention is also critical, a complete helloworld example should demonstrate the bestpartice.

KWWidgets convertion

• TODO Review which widgets should be converted
• Static widgets: Multicolumn color table, ...

Histogram / plot widgets

• Option1: CTK/Qt - with interface to import data from VTK to CTK
• Option2: Discuss with vtkChart folks and coordinare conversion of existing widgets from CTK to vtkChart.

Item list

• J2 is the Chart guy: Work in // with vtkChart folks
• Jc: Infrastructure / CDash support / Python*
• Seb / Danielle: Workflow manager
• Kitware will come up with mile stones for project at next weeks meeting