Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Pmf"

(New page: = PMF Project = == Tropics == * Architecture * User cases * PMF Model * Code generation)
 
(EclipseCon2010)
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= PMF Project =
+
Presentation Modeling Framework aims at simplifying UI development using a model driven approach. UI development can be split up into three stages:
== Tropics ==
+
 
* [[PMF/Architecture|Architecture]]
+
#Functional specification where the UI concepts are independent of any UI technology
* [[PMF/UserCase|User cases]]
+
#Translation from the functional specification to a technical widget set and platform
* [[PMF/model|PMF Model]]
+
#Layout and styling
* [[PMF/generation|Code generation]]
+
 
 +
In current practice these are mostly taken in a single step using a single technology. We plan to provide the right tooling support for each step using models at different levels.
 +
 
 +
*[[PMF/Architecture|Architecture]]
 +
*[[PMF/design|PMF Design]]  
 +
*[[PMF/UserCase|Use cases]]  
 +
*[[PMF/Target Platforms|Target Platforms]]
 +
*[[PMF/Example Applications|Example Applications]]
 +
 
 +
== Info  ==
 +
 
 +
=== EclipseCon2010 ===
 +
* PMF [http://wiki.eclipse.org/images/d/d9/PMF.pdf Deck] [http://www.soyatec.org/eclipse/eclipsecon2010/PMF/PMF.html Demo]
 +
* [http://www.slideshare.net/BENOIT_LANGLOIS/ui-modeling-in-action-with-pmf-e4xwt-and-egf UI Modeling in action with PMF, EGF and e4/XWT]
 +
 
 +
== Work Areas  ==
 +
*[[PMF/model|Model]]
 +
*[[PMF/tools|Tools]]  
 +
*[[PMF/generation|Code Generation]]

Revision as of 12:26, 24 March 2010

Presentation Modeling Framework aims at simplifying UI development using a model driven approach. UI development can be split up into three stages:

  1. Functional specification where the UI concepts are independent of any UI technology
  2. Translation from the functional specification to a technical widget set and platform
  3. Layout and styling

In current practice these are mostly taken in a single step using a single technology. We plan to provide the right tooling support for each step using models at different levels.

Info

EclipseCon2010

Work Areas

Back to the top