Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Riena/Navigation"
(→Module Groups, Modules and Submodules) |
(→Module Groups, Modules and Submodules) |
||
Line 21: | Line 21: | ||
Selecting a subapplication, module group or module automatically activates the first submodule within that context. This implies the there is no work area associated with modules, module groups or subapplications - only submodules can have an associated work area (ie view and optionally a controller) | Selecting a subapplication, module group or module automatically activates the first submodule within that context. This implies the there is no work area associated with modules, module groups or subapplications - only submodules can have an associated work area (ie view and optionally a controller) | ||
|} | |} | ||
+ | |||
+ | The Riena navigation therefore can be thought of as a tree where the root is the application node and the leafs are the subapplication nodes. |
Revision as of 11:37, 3 December 2008
The goal of the Riena navigation concept is to make navigation as easy and comfortable as possible for the enterprise user.
Subapplications
The Riena application ist made up from possibly multiple subapplications identifyable by the handles in the top area of the application window.
This example shows a Riena client application with 2 subapplications called 'Navigation' and 'Playground'. The 'Navigation' subapplication is currently selected.
Module Groups, Modules and Submodules
Each subapplication may contain multiple module groups, each module group may contain multiple modules and each module may contain multiple submodules.
The Riena navigation therefore can be thought of as a tree where the root is the application node and the leafs are the subapplication nodes.