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"
(→Static content) |
(→Control flow) |
||
Line 10: | Line 10: | ||
=== Control flow === | === Control flow === | ||
− | + | Control flow deals with 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. | |
== Page flow design == | == Page flow design == |
Revision as of 07:14, 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
Static content
UI structure and appearance doesn't change in its whole life circle. It mainly deals with a presentation structure. It is a simplest case. In a real application, this case is very rare. But it is a foundation of dynamic UI design.
Control flow
Control flow deals with 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.