Difference between revisions of "2011 Project Week Breakout Session: Slicer4"
From NAMIC Wiki
| Line 36: | Line 36: | ||
* Porting remaining SWidgets (Crosshairs, Model/Slice Intersections, Reformat Widget...) | * Porting remaining SWidgets (Crosshairs, Model/Slice Intersections, Reformat Widget...) | ||
* Removing slicer3 legacy code from slicer4 repository | * Removing slicer3 legacy code from slicer4 repository | ||
| + | * What modules from the core should become extensions? | ||
===Meeting Notes:=== | ===Meeting Notes:=== | ||
Revision as of 15:00, 10 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
- Remote IO options (save/restore of slicer data and scenes via DICOM, Midas, wiki...)
- 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?
- 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?
