User:Andrew/LayoutPatterns/CommandPatterns: Difference between revisions
No edit summary |
|||
| Line 15: | Line 15: | ||
===Patterns for a complex command structure=== | ===Patterns for a complex command structure=== | ||
[[CP-Toolbar+MenuButton.png]] | [[File:CP-Toolbar+MenuButton.png]] | ||
* Use Toolbar + Menu Button when it is not necessary to expose the root commands. Toolbar exposes frequently used commands. | * Use Toolbar + Menu Button when it is not necessary to expose the root commands. Toolbar exposes frequently used commands. | ||
* Commands are also exposed by direct manipulation of content, context menus or a context panel. | * Commands are also exposed by direct manipulation of content, context menus or a context panel. | ||
Revision as of 02:15, 21 July 2014
Purpose
Command patterns are determined by the command structure chosen for the application (simple, complex or very complex). Commands are defined as any function performed by the application based on user input.
Guidelines
Patterns for a simple command structure
- Use Menu Button when there are few globally applicable commands.
- Use Context Menu or Context Panel for commands specific to selected content.
- Commands are also exposed by direct manipulation of content.
Examples
Audio/Music player, Image browser, Document viewer, Maps, Games, Contacts, Chat client, Video conference, Settings, Address book, Chat client, Terminal, Software installer, Calculator
Patterns for a complex command structure
- Use Toolbar + Menu Button when it is not necessary to expose the root commands. Toolbar exposes frequently used commands.
- Commands are also exposed by direct manipulation of content, context menus or a context panel.
Examples
Web browser, File manager, Text editor, Email, Calendar, Image editor, Archiver