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) |
(→Page/Window content design) |
||
| Line 5: | Line 5: | ||
== 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. In the context of PMF, a page is already associated with a data to present. |
=== Static content === | === Static content === | ||
| − | UI structure and appearance doesn't change in | + | UI structure and appearance doesn't change in the whole life circle. It mainly focus on a UI structure and presentation organization. It is in fact a simplest case. In a real application, this case is very rare. But this step set up the foundation of dynamic UI design. |
=== Control flow === | === Control flow === | ||
Revision as of 19:03, 30 October 2009
Contents
Development process
Based on UI structure, a UI Presentation can be divided 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. In the context of PMF, a page is already associated with a data to present.
Static content
UI structure and appearance doesn't change in the whole life circle. It mainly focus on a UI structure and presentation organization. It is in fact a simplest case. In a real application, this case is very rare. But this step set up the foundation of dynamic UI design.
Control flow
Control flow deals with the dynamic aspect of UI page content. For example, in a payment page of purchase order, the mode of payment UI depends on the type of credit card. When you select one mode, the corresponding UI should be displayed in the same page.