Difference between revisions of "2016 Winter Project Week/Projects/Workflows"

Latest revision as of 14:57, 8 January 2016

Objective	Approach and Plan	Progress and Next Steps
Implement a reusable mechanism to work with workflows in Slicer that navigate between different modules Implement an easily extensible and customizable GUI	Discuss what would be the best approach from a GUI point of view Implement an abstract module class that other modules could instantiate to implement a custom workflow Discuss what would be the best way of persisting the state of the workflow (see Data Persisting project)	Slicelets and total customization of the Slicer UI seem to be a good approach to implement workflows (from a GUI point of view). It looks too hard to generalize a GUI for every workflow ("CLI style") One of the best options for Python modules seems to be extending the ScriptedLoadableModule classes, adding input/output parameters and a "run" method, following a similar architecture than CLIs

This project can be closely coupled with Data Persisting project

@@ Line 7: / Line 7: @@
 ==Key Investigators==
 * Raúl San José
 * Jorge Onieva
+* Hans Meine (interested observer)
 ==Project Description==
@@ Line 26: / Line 27: @@
 |
 <!-- Fill this out at the end of Project Week; describe what you did this week and what you plan to do next -->
-*
+*Slicelets and total customization of the Slicer UI seem to be a good approach to implement workflows (from a GUI point of view). It looks too hard to generalize a GUI for every workflow ("CLI style")
+* One of the best options for Python modules seems to be extending the ScriptedLoadableModule classes, adding input/output parameters and a "run" method, following a similar architecture than CLIs
 |}