Difference between revisions of "Slicer3:IGTdesign"
From NAMIC Wiki
Line 3: | Line 3: | ||
[[2007_December_Slicer_IGT_Programming| '''<< back to Slicer IGT Programming Event''']] | [[2007_December_Slicer_IGT_Programming| '''<< back to Slicer IGT Programming Event''']] | ||
− | == | + | ==Slicer UI for IGT applications== |
− | + | ||
− | + | === Slicer "base" UI functionality === | |
− | + | (list) | |
− | + | ||
+ | === "specialized" Slicer UI functionality === | ||
+ | (list) | ||
==Process:== | ==Process:== |
Revision as of 17:05, 13 December 2007
Home < Slicer3:IGTdesignContents
IGT breakout session for Slicer interface
<< back to Slicer IGT Programming Event
Slicer UI for IGT applications
Slicer "base" UI functionality
(list)
"specialized" Slicer UI functionality
(list)
Process:
- develop understanding of user needs (today's primary goal)
- refract through engineering constraints
- develop design plan
- get user feedback
- implement
- test, feedback, refinements, repeat.
For discussion:
Are topics below appropriate, and what’s missing?
Displaying essential information:
- what information should be exposed?
- what information can/should be present but hidden?
- what information should be removed?
Providing access to essential functionality:
- is there a “core” set of functionality?
- how to configure core environment?
- how to expose “hot-load” for additional functionality?
Allowing ability to configure layout for different applications:
- list layout requirements by application -> table to distill
- discuss multi-window versus consolidated display
- additional layout/display requirements: fonts, colors, audio, etc.?
Providing appropriate workflow support:
- feedback on existing workflow wizard
Determine good mechanism for ongoing discussion: wiki? Mailing list? Tcon?