|
|
| (56 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| ==Layout Patterns==
| | '''NOTE:''' The content of the page has been moved to [[User:Andrew/Layout]]. |
| | |
| The complete layout for your application may be constructed by selecting an appropriate Command Pattern and Navigation Pattern. | |
| * [[User:Andrew/LayoutPatterns/CommandPatterns|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.
| |
| *[[User:Andrew/LayoutPatterns/NavigationPatterns|Navigation Patterns]] are determined by the information structure of the application content (flat, 2-deep, 3-deep, n-deep). See the tables below to determine the best navigation pattern for your application.
| |
| | |
| ===Plasmoids===
| |
| Plasmoids like panel popups and desktop widgets should meet the following criteria:
| |
| * Plasmoids use only a [[User:Andrew/LayoutPatterns/CommandPatterns#Patterns_for_a_simple_command_structure|simple command structure]].
| |
| * The content of plasmoids must have a flat or 2-deep information structure.
| |
| * If the above two criteria cannot be satisfied, consider designing a traditional desktop application instead of a plasmoid.
| |
| | |
| ===Notes===
| |
| * When starting design on a new application, it may not be clear what the command structure should be. Start with a simple command structure. As the design develops, consider a more complex command pattern only if it’s necessary.
| |
| * The n-deep navigation patterns may also be used for the 2-deep and 3-deep patterns.
| |
Latest revision as of 18:20, 23 July 2014
