User:Lantiga

Ideas for Slicer3

• Transforms and CLI:
  • the rationale is to give command line modules a chance not to worry about transforms but still have correct information available as to spacing and up/down, left/right, front/back consistency
  • the image passed to a command line module should be in normalized orientation space, i.e.: real origin, real spacing,
  • reference node specified in XML (either tag of the reference node or tag of child nodes to the reference - the latter allows many references in the same command line). Images in normalized orientation space.

• Multi-stage CLI:
  • wizard or tabbed interface with content generated one page per command line module, and user control is returned from one page to the next.
  • one XML that puts command line modules together. This way command line modules can be either used alone or in a wizard.
  • change the way CLI are specified: XML files are discovered first, each XML describes how's the module is going to be (executable, shared library, Python class, etc). This saves time for module discovery (at least on OSX), and (as suggested by Raoul) it makes it easy for a developer to know how that CLI is going to behave and to develop against it.

• Fix vtkITK CMakeLists.txt (generate vtkITKTCL.so separately from vtkITK.so).

• XML module GUI:
  • give possibility to build a GUI from XML in ScriptedModules (either from Tcl or Python) or even everywhere in Slicer3, even from C++.

• Python:
  • try wrapping VTK. What happens when Python through Tcl is used and ShallowCopy to a true VTK module is called?