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 "PMF/design"
(→Control flow) |
|||
| Line 1: | Line 1: | ||
| + | = Development process = | ||
Based on UI structure, a UI Presentation can be divided in in two categories: | Based on UI structure, a UI Presentation can be divided in in two categories: | ||
* Page/Window content design | * Page/Window content design | ||
* Page flow design | * Page flow design | ||
| − | = Page/Window content design = | + | == Page/Window content design == |
This part deals with the content of a presentation unit. It can be a page, frame or a window | This part deals with the content of a presentation unit. It can be a page, frame or a window | ||
=== Static content === | === Static content === | ||
| Line 12: | Line 13: | ||
== Page flow design == | == Page flow design == | ||
| + | |||
| + | |||
| + | = System design = | ||
| + | == Data model connection == | ||
| + | == Presentation model == | ||
| + | == Code generation == | ||
Revision as of 19:47, 29 October 2009
Contents
Development process
Based on UI structure, a UI Presentation can be divided in in two categories:
- Page/Window content design
- Page flow design
Page/Window content design
This part deals with the content of a presentation unit. It can be a page, frame or a window
Static content
UI structure and appearance doesn't change in the whole life circle. It deals with a presentation structure. It is a simplest case. But in a real application, this case is very rare. But it is a foundation of dynamic UI design.
Control flow
This part deals with the UI evolution through time.