ParaQ:Telecon 09/13/2005 1PM EST: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
m (→Demo Script) |
|||
| Line 47: | Line 47: | ||
|- | |- | ||
|- | |- | ||
| 1 | ! align="left" valign="top" | 1 | ||
| Click on ParaQ Icon, which brings up application quickly. The interface is very simple, with a minimum of child windows included. There is at least one toolbar present, which is the macro toolbar. This is populated several macros, which appear as icons. | | Click on ParaQ Icon, which brings up application quickly. The interface is very simple, with a minimum of child windows included. There is at least one toolbar present, which is the macro toolbar. This is populated several macros, which appear as icons. | ||
| Shows loading of simplified UI state, and user-editable macros (from a pre-defined location) | | Shows loading of simplified UI state, and user-editable macros (from a pre-defined location) | ||
Revision as of 14:33, 8 September 2005
Agenda
| Item | People | Description |
|---|---|---|
| 1 | KMor | Multiview update |
| 2 | CM | Report on testing solution for Qt. See #Qt Testing Requirements |
| 3 | CM | Present straw man class architecture for ParaView Server API |
| 4 | BW,DR | Present demo script |
| 5 | DR | Present Microsoft Project schedule overview |
| 6 | BW | Update on videocon equipment |
Pre-Meeting Information
Demo Script
This demo is to be executed on Windows XP.
| Step | Description | Purpose | |
|---|---|---|---|
| 1 | Click on ParaQ Icon, which brings up application quickly. The interface is very simple, with a minimum of child windows included. There is at least one toolbar present, which is the macro toolbar. This is populated several macros, which appear as icons. | Shows loading of simplified UI state, and user-editable macros (from a pre-defined location) | |
| 2 | File->Open, browse to ParaQ xml file, and open it. This loads a complete configuration, including linked views, positions of toolbars, and attributes (such as timestep, current variable, etc.) that are needed to define the current state. | Shows loading of previous state. | |
Qt Testing Requirements
- Test for code coverage.
- Test GUI's interaction with server manager.
- Test GUI itself (e.g. button click leads to correct action & results) that's insensitive to layout.
- Easy to create test cases.
- Community's ability to test and contribute to testing.
- Integration with vtk's and paraview's testing framework (meaning leverage testing abilities already existent such as image comparisons and such)
- Drive demos, using the same framework.
