High Level Usability Goals: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 1: Line 1:
We wish to identify some high level usability goals for:
We wish to identify some high level usability goals for:
 
* A ParaView replacement
- A ParaView replacement
* Longer range ParaQ planning
 
- Longer range ParaQ planning


Goals:
Goals:
 
* User Interface responsiveness for large data (e.g. Accept/Reset)
- User Interface responsiveness for large data (e.g. Accept/Reset)
* Quick navigation between object inspectors (e.g. between sources, filters, lookup table editors)
 
* Intuitive parameter editing (of readers, filters, lookup tables, annotation, composite filters etc. using Qt GUI + 3D widgets)
- Quick navigation between object inspectors (e.g. between sources, filters, lookup table editors)
* Time selection (global time?)
 
* Intuitive data inspection
- Intuitive parameter editing (of readers, filters, lookup tables, annotation, composite filters etc. using Qt GUI + 3D widgets)
* Easy animation (but also powerful)
 
* Easy quantitative analysis
- Time selection (global time?)
 
- Intuitive data inspection
 
- Easy animation (but also powerful)
 
- Easy quantitative analysis

Revision as of 13:52, 3 March 2006

We wish to identify some high level usability goals for:

  • A ParaView replacement
  • Longer range ParaQ planning

Goals:

  • User Interface responsiveness for large data (e.g. Accept/Reset)
  • Quick navigation between object inspectors (e.g. between sources, filters, lookup table editors)
  • Intuitive parameter editing (of readers, filters, lookup tables, annotation, composite filters etc. using Qt GUI + 3D widgets)
  • Time selection (global time?)
  • Intuitive data inspection
  • Easy animation (but also powerful)
  • Easy quantitative analysis