Difference between revisions of "Projects:ARRA:SlicerEM Meeting 07082010"

From NAMIC Wiki
Jump to: navigation, search
(Created page with 'Meeting Note Attendant: * Stephen Aylward * Sebastien Barre * Jean-Christophe Fillion-Robin * Julien Finet * Danielle Pace = Workflow Manager = Should be incorporated into CTK…')
 
Line 11: Line 11:
 
Should be incorporated into CTK
 
Should be incorporated into CTK
 
. There are two options:
 
. There are two options:
−
* Option1: Keep VTK "stuff
+
* Option1: Keep VTK "stuff"
−
 
 
 
* Option2: just go ahead and convert to full Qt
 
* 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 cuold then been expored as QtDesigner pluing or promoted.
  
−
It resumes Option2 is the best. Sebastien has already some generic classes build over QtStateMachine framework that he could re-use.  
+
== 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.
−
* Design of UI should done using QtDesigner. The discussed solution will consist in having a UI file with a stacked widget where each step would be a layer in the stack.
+
* The wizzard will implement a convenience layer to make sure a given state is completed before switching to the next step.
−
* Create a "rock-solid" hello world example to illustrate the bestpractice and which naminc convention should be applied.
+
* Naming convention is also critical, a complete helloworld example should demonstrate the bestpartice.  
−
 
 
−
 
 
−
 
 
−
  - Convenience layer to make sure a state is complete before  
 
−
 
 
−
transition.
 
−
 
 
−
 
 
−
 
 
−
  - Seb has done some work for Michel
 
−
 
 
−
        Good: QtState machine
 
−
 
 
−
        Bad: Wizzard that currently exists won't support state machine
 
−
 
 
−
                -> Not difficult to re-design
 
−
 
 
−
 
 
−
 
 
−
 
 
  
 
= KWWidgets convertion =  
 
= KWWidgets convertion =  
−
- TODO(S) Review which widgets should be converted
+
* TODO Review which widgets should be converted
−
 
+
* Static widgets: Multicolumn color table, ...
−
- Static widgets:  
 
−
 
 
−
    - Multicolumn color table
 
−
 
 
−
 
 
−
 
 
−
 
 
−
 
 
−
= Panels =
 
−
- Color transfer function / Histo
 
−
 
 
−
  - first way: CTK/Qt only - with interface to import data from VTK to CTK
 
−
 
 
−
 
 
−
 
 
−
  - second: Marcus / vtkChart / Wip
 
−
 
 
−
      - Coordinate with Nicolas
 
−
 
 
−
          -> Won't be done in the coming two months
 
−
 
 
−
          -> Ask him to convert its work to vtkChart
 
−
 
 
−
 
 
−
 
 
−
 
 
−
= Action plan =
 
−
 
 
−
 
 
−
  - J2 is the Chart guy - Wotk in // with Marcus
 
−
 
 
−
 
−
 
 
−
  - Seb / Danielle: Workflow manager
 
−
 
 
  
 +
== 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.
  
−
  - Jc: Infrastructure / CDash support / Python*
+
= Item list =
 +
* J2 is the Chart guy: Work in // with vtkChart folks
 +
* Jc: Infrastructure / CDash support / Python*
 +
* Seb / Danielle: Workflow manager

Revision as of 14:26, 12 July 2010

Home < Projects:ARRA:SlicerEM Meeting 07082010

Meeting Note

Attendant:

  • 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 cuold 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
Retrieved from "https://www.na-mic.org/w/index.php?title=Projects:ARRA:SlicerEM_Meeting_07082010&oldid=55841"