|
|
| (14 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | = IGT breakout session for Slicer interface =
| + | <big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer3:IGTdesign here]</font></big>a |
| − | | |
| − | ==Goal: creating a useful, satisfying, extensible environment for IGT applications==
| |
| − | * displaying essential information
| |
| − | * providing access to essential functionality
| |
| − | * allowing some ability to configure layout for different applications
| |
| − | | |
| − | ==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.?
| |
| − | | |
| − | Determine good mechanism for ongoing discussion: wiki? Mailing list? Tcon?
| |
