Technical Meeting 03/30/2006 1:15PM EST
From ParaQ Wiki
Jump to navigationJump to search
Agenda
| Item | People | Description |
|---|---|---|
| 1 | Shead | Repository restructuring wrapup. |
| 2 | Group | Discuss error-handling and notification. |
| 3 | Geveci | Server connect / reconnect |
| 4 | Shead | Discuss update/reset requirements & design, see Screen Update / Undo Interaction. |
| 5 | Shead | Discuss widget naming for regression tests. |
Action Items
- Berk Geveci - Create VTK debugging macros that can be used in ParaQ objects without deriving from vtkObject.
- Tim Shead - Route all Qt debug and error output to VTK.
- Tim Shead - Create a Qt-based debug output window that will integrate well with the rest of the ParaQ UI and display all VTK errors.
- Berk Geveci - Tag the March 2006 build once Tim checks-in remaining code.
- Tim Shead - Using the new error-handling mechanisms, enforce widget naming conventions at runtime in the regression testing layer.
Discussion
- The group continued to discuss how the accept/reset mechanism would integrate with undo/redo. The discussion centered around the behavior of the Undo button when the user has made changes without hitting the "Accept" button. For April, it was agreed that, if there are changes pending, the "Undo" button will perform a "Reset" of all pending changes. If there are no changes pending, the "Undo" button will perform the next available undo on the server. The group further agreed that if a set of changes has been accepted, hitting the "Undo" button will undo the entire set of changes. Open for further discussion is whether hitting "Undo" when there are changes pending should reset all changes, or reset individual changes.
