Overall UI Design: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
| (5 intermediate revisions by 4 users not shown) | |||
| Line 19: | Line 19: | ||
* [[Compound Filters]] | * [[Compound Filters]] | ||
* [[It's views all the way down]] | * [[It's views all the way down]] | ||
* [[Selection Policy]] | |||
* [[Issues with Connection and Recent Files]] | |||
* [[Collapsible Groups]] | |||
* [[File Menu]] | |||
* [[Icon Naming Conventions]] | |||
* [[Chart Model-View]] | |||
Latest revision as of 18:25, 10 August 2006
This is a developing page that collects notes on the overal UI design
Consistency
We must have visual and widget consistency across the UI. Examples:
- When dealing with variables, we should present consistent visual and operational options. For example, any list of variables should have at a minimum the following elements. The graphical representation of these things should be consistent across the UI. For example, if we use an icon to represent type, that will be consistent whenever there is a variable list, whether that list be in a combo box, a list box, or other widget. Similarly, loaded/unloaded representation should be consistent.
- Indication of type (Element, Node, etc.)
- State (loaded, not loaded)
- Name
Specific Elements
- Exodus Reader Object Inspector
- Animation GUI
- PV Information Page Replacement
- Lookup Table Editing
- Server Connection Dialog
- Value List Widget
- File Browser
- Animation Dialogue
- Compound Filters
- It's views all the way down
- Selection Policy
- Issues with Connection and Recent Files
- Collapsible Groups
- File Menu
- Icon Naming Conventions
- Chart Model-View
