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"
(→Navigation Node Common Properties) |
(→Navigation Node Common Properties) |
||
Line 27: | Line 27: | ||
* '''id''' - the id is made up from two parts, a type and an instance part - this is explained later on this page) | * '''id''' - the id is made up from two parts, a type and an instance part - this is explained later on this page) | ||
* '''children''' - the type of children depends on the parent, a module node eg can only have submodule nodes as children | * '''children''' - the type of children depends on the parent, a module node eg can only have submodule nodes as children | ||
− |
Revision as of 12:46, 3 December 2008
Contents
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 submodule nodes.
There are some properties that can be defined for all navigation nodes:
- id - the id is made up from two parts, a type and an instance part - this is explained later on this page)
- children - the type of children depends on the parent, a module node eg can only have submodule nodes as children