| What are the best practices for moving a EMF model to a Plug-in? [message #1674340] |
Sat, 14 March 2015 18:17 |
 Paul Roubekas
Messages: 207
Registered: March 2012
Location: Chattanooga, TN USA |
Senior Member |
|
|
Newbie here. Is there documentation or a wiki page on the best practices for moving a EMF model to a Plug-in? I am building a RCP application that will have many plug-ins. Dozens maybe hundreds.
I see wiki pages that give hints that EMF is intended to work with Papayrus.
For example:
URL: https://wiki.eclipse.org/Papyrus_User_Guide
Section: Tutorials on UML modeling with Papyrus
File: " PapyrusApplyStaticProfil.PNG"
The screen capture shows a "ECore" option in the "apply profiles from Papyrus repository" selection box.
Which caused me to hunt and peck and discover the following UI actions create a set of files.
- Then I can create some Papyrus "*.cxt" and "*.xwt" files from a EMF model by performing the following steps.
- Focus in the Package Explorer a Papyrus project.
- Select the New option from the context menu.
- Expand the Papyrus Nature
- Select the "property view configuration" option.
- Press the "Next" Button.
- Select the "Create form Ecore MetaModel"
- Press the "Next" Button.
- Browse the Eclipse Workspace and find an existing EMF .ecore file.
- Press the "Ok" Button.
- Press the "Next" Button.
- Pick "Basic Method" drop down option.
- Press the "Next" Button.
- Press the "Finish" Button.
But being a newbie I no idea what to do with these files. They don't open up in a UML diagram of any sort.
Another hint that Papyrus and EMF might work together.
URL: https://wiki.eclipse.org/Papyrus_Required_External_Plugins
Section: Required Plugins
Quote: "EMF Facet "
Section: Eclipse 4.2
Quote: "EMF Compare UML2 integration - Juno update site"
Quote: "EMF Facet - Juno update site"
Quote: "EMF Model Query SDK - Juno update site"
etc...
And then there is this paragraph from the Papyrus project itself.....
Quote:Papyrus
Papyrus provides an integrated, user-consumable environment for editing any kind of EMF model and particularly supporting UML and related modeling languages such as SysML and MARTE. Papyrus provides diagram editors for EMF-based modeling languages amongst them UML 2 and SysML and the glue required for integrating these editors (GMF-based or not) with other MBD and MDSD tools. It also offers a very advanced support of UML profiles that enables users to define editors for DSLs based on the UML 2 standard and its extension mechanisms.
Q0) Is this design & development path documented anywhere?
Q1) Can a designer/developer start with Papyrus using EMF ecore classes?
Q2) Or must the EMF model be created first?
Q3) How far one must design before moving over to Papyrus?
Q4) Can EMF and Papyrus do round tripping if one just adds a "Gen" postfix to all the class methods?
Q5) Is it best to have a one-to-one relationship between the EMF models and Plug-ins?
Q6) Are the tips how to make to migration from the EMF model to the Plug-in tool easier?
Oxygen 3a
Windows 10
[Updated on: Sun, 15 March 2015 20:57] Report message to a moderator |
|
|
Powered by
FUDForum. Page generated in 0.02983 seconds
] 
Search
Help
Register
Login
Home
