Difference between revisions of "Slicer Day October 2008"

From NAMIC
Jump to: navigation, search
Line 15: Line 15:
 
** other low hanging fruits
 
** other low hanging fruits
 
* input widget interface behavior: eg. number input in transformation module
 
* input widget interface behavior: eg. number input in transformation module
* selection behavior in slicer
+
* design: clear & consistent selection behavior in slicer
 
** from user's point of view, what's a widget and what not (fiducials?)
 
** from user's point of view, what's a widget and what not (fiducials?)
** all 'selectable' things should behave in same way (what will be good?)
+
** all 'selectable' things should behave consistently (what will be good?)
 
** are datasets (like models) selectable?
 
** are datasets (like models) selectable?
 
*** if yes, how can we make their selection behavior consistent with widgets?
 
*** if yes, how can we make their selection behavior consistent with widgets?

Revision as of 06:07, 7 October 2008

Home < Slicer Day October 2008
Back to Events

Likely date: October 7

Location: 1249 Bolyston

Likely attendees: Bob O'Bara, Yumin, Will schroeder

Agenda:

  • 3D widgets in slicer
    • Bug fix for the "attention deficit" in the current ones
    • Module panels to accompany 3D widgets: How to duplicate a double oblique?
    • Potential deployment of new 3D widgets in Slicer: e.g. measurement tools (again with matched quantitative panels)
    • other low hanging fruits
  • input widget interface behavior: eg. number input in transformation module
  • design: clear & consistent selection behavior in slicer
    • from user's point of view, what's a widget and what not (fiducials?)
    • all 'selectable' things should behave consistently (what will be good?)
    • are datasets (like models) selectable?
      • if yes, how can we make their selection behavior consistent with widgets?