Difference between revisions of "2011 Project Week Breakout Session: Slicer4"
From NAMIC Wiki
Line 17: | Line 17: | ||
=== Preliminary Agenda: === | === Preliminary Agenda: === | ||
− | + | Purpose: 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 | * Review of features and next steps with the idea that developers and users can vote on priorities for development effort | ||
** Main application GUI: compare [http://wiki.slicer.org/slicerWiki/index.php/Modules:MainApplicationGUI-Documentation-3.6 Slicer 3] and Slicer 4 | ** Main application GUI: compare [http://wiki.slicer.org/slicerWiki/index.php/Modules:MainApplicationGUI-Documentation-3.6 Slicer 3] and Slicer 4 | ||
− | ***Reorganizing panels above | + | ***Reorganizing panels above both the slice viewers and 3d viewers for consistent look and feel. |
** Review keybindings and mouse behavior | ** Review keybindings and mouse behavior | ||
***Compare [http://wiki.slicer.org/slicerWiki/index.php/Modules:EventBindings-3.6 Slicer 3] and Slicer 4 | ***Compare [http://wiki.slicer.org/slicerWiki/index.php/Modules:EventBindings-3.6 Slicer 3] and Slicer 4 | ||
Line 31: | Line 31: | ||
*** Interactive Editor (Steve Pieper) | *** Interactive Editor (Steve Pieper) | ||
*** Sceneviews (xx) | *** Sceneviews (xx) | ||
− | *** Slice | + | *** Slice Controls Module: Should present controls for: Slice viewers, compare viewers, 3D viewers: rename to Layout controler? |
− | *** Slicer Welcome Module | + | *** Slicer Welcome Module: update? |
− | *** Volume Rendering Module | + | *** Volume Rendering Module: I/O should have same user experience as I/O in Slice viewers |
*** Volumes Module (xx) | *** Volumes Module (xx) | ||
*** Transforms Module (xx) | *** Transforms Module (xx) |
Revision as of 12:21, 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:
Purpose: 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: compare Slicer 3 and Slicer 4
- Reorganizing panels above both the slice viewers and 3d viewers for consistent look and feel.
- Review keybindings and mouse behavior
- Compare Slicer 3 and Slicer 4
- Identify inconsistencies
- Current List of Core modules
- Annotation Module (xx)
- Color Module (xx)
- Data Module (xx)
- Interactive Editor (Steve Pieper)
- Sceneviews (xx)
- Slice Controls Module: Should present controls for: Slice viewers, compare viewers, 3D viewers: rename to Layout controler?
- Slicer Welcome Module: update?
- Volume Rendering Module: I/O should have same user experience as I/O in Slice viewers
- Volumes Module (xx)
- Transforms Module (xx)
- Main application GUI: compare Slicer 3 and Slicer 4
- Infrastructure discussions
- instrumenting dimensions for sliders, seeds etc.: Slicer users have data with a wide range of dimensions. Mouse ** 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)
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?