Difference between revisions of "2008 Winter Project Week:KWWidgets"

From NAMIC Wiki
Jump to: navigation, search
Line 43: Line 43:
  
 
* GUI Testing
 
* GUI Testing
** See the Wiki, lots of products were evaluated
+
** See the [http://www.kwwidgets.org/Wiki/KWWidgets/GUI_Testing GUI Testing/Tracing] wiki, lots of products were evaluated
 
** None of them inspects deep enough to support KWWidgets
 
** None of them inspects deep enough to support KWWidgets
** We *really* need to roll our own (see the feature requests in the Wiki page)
+
** We *really* need to roll our own, but we have the list of features and what UI should look like.
 
</div>
 
</div>
  

Revision as of 21:58, 10 January 2008

Home < 2008 Winter Project Week:KWWidgets
KWWidgets GUI Toolkit


Key Investigators

  • Kitware: Sebastien Barre
  • BWH: Wendy Plesniak, Katie Hayes

Objective

Evaluate the current roadmap, determine which items need to be added to achieve specific Slicer3 goals, review pending problems like UI testing.

Approach, Plan

Discussion is open to everyone with a specific need to be addressed in the current KWWidgets widget set. We will also discuss various GUI Testing/Tracing frameworks.

Progress

  • Bug Fixes
    • Filebrowser on 64 bits Unix
    • Double-click in multicolumn fields (Unix)
    • Garbled icons on some Linux systems
  • Feature Requests
    • Steve: Range widget => Control/Shift key to increment by 1/10, 1/100 of the current increment. Rational: the range may be numerically large but visually small on screen, making 1 pixel increment too big.
    • Wendy: Cookbook UI
    • Jim: Spinbox widget => ability to change the default increment (either with Shift/Control, or menu)
    • Andy/Ron: Range widget => ability to change the color of both ends
    • Ron: new color picker, with color presets/favs
    • Douglas: support for NaN
    • Steve: UI for event broker
  • GUI Testing
    • See the GUI Testing/Tracing wiki, lots of products were evaluated
    • None of them inspects deep enough to support KWWidgets
    • We *really* need to roll our own, but we have the list of features and what UI should look like.



References

  • to be entered here