Demo:UI Development: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
|||
| Line 3: | Line 3: | ||
==Components== | ==Components== | ||
# Window management toolbar. Much like the toolbar in Prism, this toolbar has button for several actions the user can take when creating, deleting, or otherwise manipulating windows. First pass should duplicate Prism's toolbar. Later passes will be revised per group/user input. | |||
# Compound Filter toolbar. This toolbar shows several icons, representing the Compound Filters found in a designated directory. These should operate on appropriate selected objects, or they should bring up UI that enables them to operate. For example, if the CF needs a vtkDataSet input, if a vtkDataSet is selected (say, in the Hierarchy editor), this CF button will be enabled. | |||
Revision as of 17:55, 9 November 2005
Overview
This page captures the UI components and capabilities required by the Demo:Script. In general, the ParaQ client and its UI is intended to convey that it is a configurable, useful tool. It should be the opposite of ParaView, Maya - tools that present a bewildering array of controls, navigable only by expert users. Instead, the UI should be simple. It should respond logically to user actions. And, it should look neat, professional, and (where appropriate) whizzy.
Components
- Window management toolbar. Much like the toolbar in Prism, this toolbar has button for several actions the user can take when creating, deleting, or otherwise manipulating windows. First pass should duplicate Prism's toolbar. Later passes will be revised per group/user input.
- Compound Filter toolbar. This toolbar shows several icons, representing the Compound Filters found in a designated directory. These should operate on appropriate selected objects, or they should bring up UI that enables them to operate. For example, if the CF needs a vtkDataSet input, if a vtkDataSet is selected (say, in the Hierarchy editor), this CF button will be enabled.
