Term
|
Definition
- Visual representaiton of users task
- organized in a sensible way |
|
|
Term
| What kind of menu structures exist? |
|
Definition
- Linear
- Simultaneous
- Hierarchical |
|
|
Term
|
Definition
| prefer breadth (no. of items per level) over depth (no. of levels (no more than 3)) |
|
|
Term
|
Definition
- Change visual layout
- Selection gestures
- Animated visual cue (e.g. make non-selectable stuff transparent) |
|
|
Term
| How do Command interfaces work? |
|
Definition
- User issues textual command and watches what happens
- If result is correct, next command is issued
- Otherwise, some other strategy is adopted |
|
|
Term
| Pros of command interfaces |
|
Definition
- Efficient fo batch processing
- Composition and output redirection possible
- Easy to track history
- Easy to automate |
|
|
Term
| Cons of command interfaces |
|
Definition
| - Users must recall commands and syntax |
|
|
Term
|
Definition
- one command, one task
- Follow each command by one or more arguments (adds options to customize)
- Organize command in menu structure |
|
|
Term
| How should command interfaces be designed? |
|
Definition
- Use consistent argument order
- Flexible option order
- Provide help (standard documentation system/syntax (--help), show help on parsing error) |
|
|
Term
|
Definition
- simple truncation: use first, second, third letters (manual -> man)
- vovel drop with simple truncation (remove -> rm)
- first and final letter (sort -> ST)
- first letter of each word in a phrase (make directory -> md)
- Standard abbreviations (quantity -> qty) |
|
|
