Technical Meeting 09/14/2006 1:15PM EDT: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 19: | Line 19: | ||
== Action Items == | == Action Items == | ||
* Tim - remind Dave Rogers about Prism in CVS every day! | |||
* Get rid of array information in the "color by" combo box. | |||
* Berk - statistics view will be "off" by default. | |||
* Retain dockable window sizes, and have sensible defaults. | |||
* Tim - explore QSettings limitations, whether we can force QSettings to always save to the filesystem. | |||
== Discussion == | == Discussion == | ||
* The team discussed options for displaying statistics: | |||
** We will remove array information from the "color by" combo box because it isn't needed when choosing what to color by. | |||
** We will add array range information to the lookup table user interface because that's when users care about ranges. | |||
** We will beef-up the statistics panel to include additional drill-down data such as arrays, min/max, min/max over all timesteps, etc. | |||
* The team discussed lookup table requirements and how they should be stored & shared. | |||
Revision as of 14:14, 14 September 2006
Agenda
| Item | People | Description |
|---|---|---|
| 1 | Geveci | Team Status |
| 2 | ||
| 3 | ||
| 4 |
Action Items
- Tim - remind Dave Rogers about Prism in CVS every day!
- Get rid of array information in the "color by" combo box.
- Berk - statistics view will be "off" by default.
- Retain dockable window sizes, and have sensible defaults.
- Tim - explore QSettings limitations, whether we can force QSettings to always save to the filesystem.
Discussion
- The team discussed options for displaying statistics:
- We will remove array information from the "color by" combo box because it isn't needed when choosing what to color by.
- We will add array range information to the lookup table user interface because that's when users care about ranges.
- We will beef-up the statistics panel to include additional drill-down data such as arrays, min/max, min/max over all timesteps, etc.
- The team discussed lookup table requirements and how they should be stored & shared.
