Difference between revisions of "2011 Project Week Breakout Session: Slicer4"
From NAMIC Wiki
Line 20: | Line 20: | ||
* Review of features and next steps with the idea that developers and users can vote on priorities for development effort | * Review of features and next steps with the idea that developers and users can vote on priorities for development effort | ||
− | ** [http://www.slicer.org/slicerWiki/index.php/Slicer4:Remote_Data_Handling Remote IO options] (save/restore of slicer data and scenes via DICOM, Midas, wiki...) | + | ** Main application GUI |
+ | ** Keybindings, mouse behavior: compare Slicer 3 and Slicer 4 | ||
+ | **List of Core modules | ||
+ | *** Annotation Module (xx) | ||
+ | *** Color Module (xx) | ||
+ | *** Data Module (xx) | ||
+ | *** Interactive Editor (Steve Pieper) | ||
+ | *** Sceneviews (xx) | ||
+ | *** Slice Controlls Module (x) | ||
+ | *** Slicer Welcome Module (xx) | ||
+ | *** Volume Rendering Module (xx) | ||
+ | *** Volumes Module (xx) | ||
+ | *** Transforms Module (xx) | ||
+ | |||
+ | * Infrastructure discussions | ||
+ | ** [http://www.slicer.org/slicerWiki/index.php/Slicer4:Remote_Data_Handling Remote IO options] (save/restore of slicer data and scenes via DICOM, Midas, wiki...): Use a zip ball with a Dicom header and some thumbnails? | ||
** Performance enhancements/bottlenecks | ** Performance enhancements/bottlenecks | ||
** Documentation | ** Documentation | ||
Line 32: | Line 47: | ||
*** I/O registration in qSlicer[Core]IOManager | *** I/O registration in qSlicer[Core]IOManager | ||
*** Official module for each node type "Edit properties..." ([http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=16922 current hack]) | *** Official module for each node type "Edit properties..." ([http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=16922 current hack]) | ||
+ | ** instrumenting dimensions for sliders, seeds etc.: Slicer users have data with a wide range of dimensions. Mouse DTI needs different defaults than human DTI, for instance. | ||
** web/mobile deployment options? | ** web/mobile deployment options? | ||
** other ideas or requests? | ** other ideas or requests? |
Revision as of 11:46, 14 June 2011
Home < 2011 Project Week Breakout Session: Slicer4Contents
Summer Project Week Breakout Session: Slicer4 Module Usability
9am-11am, Tuesday June 21, 2011, Star room.
Attendees:
All Slicer4 developers.
Reference Material:
Preliminary Agenda:
- Step by step review of existing slicer4 functionality and user interface with an eye towards creating a consistent and pleasant user experience with a logical grouping of functions to accomplish standard tasks.
- Review of features and next steps with the idea that developers and users can vote on priorities for development effort
- Main application GUI
- Keybindings, mouse behavior: compare Slicer 3 and Slicer 4
- List of Core modules
- Annotation Module (xx)
- Color Module (xx)
- Data Module (xx)
- Interactive Editor (Steve Pieper)
- Sceneviews (xx)
- Slice Controlls Module (x)
- Slicer Welcome Module (xx)
- Volume Rendering Module (xx)
- Volumes Module (xx)
- Transforms Module (xx)
- Infrastructure discussions
- Remote IO options (save/restore of slicer data and scenes via DICOM, Midas, wiki...): Use a zip ball with a Dicom header and some thumbnails?
- Performance enhancements/bottlenecks
- Documentation
- Enhancements to module functionality
- command line modules (slicer execution model)
- extensions
- python scripting
- Embedding slicer4 packages in standard python interpreter
- Support for new datatypes?
- Icon associated with each datatype
- I/O registration in qSlicer[Core]IOManager
- Official module for each node type "Edit properties..." (current hack)
- instrumenting dimensions for sliders, seeds etc.: Slicer users have data with a wide range of dimensions. Mouse DTI needs different defaults than human DTI, for instance.
- web/mobile deployment options?
- other ideas or requests?
General Slicer4 TODO items for discussion among developers
- Porting remaining SWidgets (Crosshairs, Model/Slice Intersections, Reformat Widget...)
- Removing slicer3 legacy code from slicer4 repository
- What modules from the core should become extensions?