Difference between revisions of "Special topic breakout: KWWidgets"
| Line 31: | Line 31: | ||
= Specific Issues = | = Specific Issues = | ||
| − | + | == From Nicole Aucoin== | |
Directory selection dialog box on linux: | Directory selection dialog box on linux: | ||
| Line 38: | Line 38: | ||
- request: an entry box where I can type a path to reduce clicking through the tree (useful before setting up a favourite) | - request: an entry box where I can type a path to reduce clicking through the tree (useful before setting up a favourite) | ||
| − | + | == From Curtis Lisle== | |
idea #1 - I have had trouble initializing widgets to specific values | idea #1 - I have had trouble initializing widgets to specific values | ||
in advance of user input. For example, I've created interfaces with | in advance of user input. For example, I've created interfaces with | ||
| Line 55: | Line 55: | ||
when the input changed. | when the input changed. | ||
| − | + | == From Brad Davis == | |
File selection dialog boxes: same on windows and linux | File selection dialog boxes: same on windows and linux | ||
File selection dialog boxes: allow selection of multiple files in windows | File selection dialog boxes: allow selection of multiple files in windows | ||
| Line 61: | Line 61: | ||
Double-clicking does not work with slicer3 and linux | Double-clicking does not work with slicer3 and linux | ||
| − | + | ==From Alex:== | |
Creating GUI performance in slicer3 | Creating GUI performance in slicer3 | ||
Customizable tree widget similar to slicer2 model hierarchy editor | Customizable tree widget similar to slicer2 model hierarchy editor | ||
| − | + | ==From Wendy:== | |
Creating special versions of menubutton drop-down menus with scroll capability, checkbuttons and radiobuttons with consistent "on/off" visual representation across platforms. (either special Slicer widgets or KWWidgets). It would be good to decide on a strategy for addressing these things. | Creating special versions of menubutton drop-down menus with scroll capability, checkbuttons and radiobuttons with consistent "on/off" visual representation across platforms. (either special Slicer widgets or KWWidgets). It would be good to decide on a strategy for addressing these things. | ||
| − | + | == From KWW-Users mailing list== | |
http://public.kitware.com/pipermail/kwwidgets/2007-June/000456.html | http://public.kitware.com/pipermail/kwwidgets/2007-June/000456.html | ||
| Line 82: | Line 82: | ||
http://public.kitware.com/pipermail/kwwidgets/2007-May/000433.html | http://public.kitware.com/pipermail/kwwidgets/2007-May/000433.html | ||
| − | + | == From Steve:== | |
Discussion of [http://www.kwwidgets.org/Wiki/KWWidgets/Tracing GUI Tracing]. In slicer3 we've started to experiment with a MRML-based tracing structure using the scene snapshot infrastructure, but we should consider if this is preferable to a GUI-based solution or not. See, for example, [http://www.na-mic.org/ViewVC/index.cgi/trunk/Base/GUI/vtkSlicerRecordSnapshotWidget.cxx?annotate=3621 the vtkSlicerRecordSnapshotWidget]. | Discussion of [http://www.kwwidgets.org/Wiki/KWWidgets/Tracing GUI Tracing]. In slicer3 we've started to experiment with a MRML-based tracing structure using the scene snapshot infrastructure, but we should consider if this is preferable to a GUI-based solution or not. See, for example, [http://www.na-mic.org/ViewVC/index.cgi/trunk/Base/GUI/vtkSlicerRecordSnapshotWidget.cxx?annotate=3621 the vtkSlicerRecordSnapshotWidget]. | ||
Revision as of 22:12, 19 June 2007
Home < Special topic breakout: KWWidgets
KWWidgets Breakout Session
June 26th, 1-2pm
Location: Grier Rooms A & B: 34-401A & 34-401B
Attendees:
- Yumin Yuan
- Steve Pieper
- Alex Yarmarkovich
- Wendy Plesniak
- Nicole Aucoin
- Curt Lisle
- Csaba Csoma
- Brad Davis
- David Gobbi
- Kiran Shivanna
- Kevin Teich
Contents
Agenda
- Roadmap (to help KWWidgets developers prioritize their work)
- Widget feature requests / feedback
- Talk about best approaches to making some widget behavior appear consistent across platforms.
- Separate Tutorial Session for New Users (to happen possibly on Wednesday)
Specific Issues
From Nicole Aucoin
Directory selection dialog box on linux:
- it pops up with a default width such that the right scroll bar isn't visible.
- request: an entry box where I can type a path to reduce clicking through the tree (useful before setting up a favourite)
From Curtis Lisle
idea #1 - I have had trouble initializing widgets to specific values in advance of user input. For example, I've created interfaces with sliders and buttons but I have had trouble getting the widgets to initialize in a state different then the default state. For example, setting a slider to value=26 in the middle of its range without dragging the mouse. The API looks like it is there, but I couldn't get it to work for me. I'm sure I tried setting the state before and after creation, if I remember, but no luck. It may be that I'm not updating the GUI successfully after changing values.
idea #2 - discuss when UI elements need to have Modified() / Update() invoked to refresh their appearance. I used a histogram widget on a project and had to experiment a lot calling the panel and RenderWidowWidget, etc. before I finally got the histogram to update when the input changed.
From Brad Davis
File selection dialog boxes: same on windows and linux File selection dialog boxes: allow selection of multiple files in windows
Double-clicking does not work with slicer3 and linux
From Alex:
Creating GUI performance in slicer3
Customizable tree widget similar to slicer2 model hierarchy editor
From Wendy:
Creating special versions of menubutton drop-down menus with scroll capability, checkbuttons and radiobuttons with consistent "on/off" visual representation across platforms. (either special Slicer widgets or KWWidgets). It would be good to decide on a strategy for addressing these things.
From KWW-Users mailing list
http://public.kitware.com/pipermail/kwwidgets/2007-June/000456.html
http://public.kitware.com/pipermail/kwwidgets/2007-June/000457.html
http://public.kitware.com/pipermail/kwwidgets/2007-June/000460.html
http://public.kitware.com/pipermail/kwwidgets/2007-June/000461.html
http://public.kitware.com/pipermail/kwwidgets/2007-June/000462.html
http://public.kitware.com/pipermail/kwwidgets/2007-May/000433.html
From Steve:
Discussion of GUI Tracing. In slicer3 we've started to experiment with a MRML-based tracing structure using the scene snapshot infrastructure, but we should consider if this is preferable to a GUI-based solution or not. See, for example, the vtkSlicerRecordSnapshotWidget.
