Hi everyone. I'm trying to find the source code with the models of UML diagrams inside eclipse modeling version because I have to develop a set of plugins with a particular dsl and the elements need to be viewed like an UML profile. Any idea where i can find them?. I would like to reuse the models and part of the code and obtain ideas from there. Regards!
> Hi everyone. I'm trying to find the source code with the models of UML
> diagrams inside eclipse modeling version because I have to develop a set
> of plugins with a particular dsl and the elements need to be viewed like
> an UML profile. Any idea where i can find them?. I would like to reuse
> the models and part of the code and obtain ideas from there. Regards!
the plugin 'org.eclipse.uml2.diagram.def' contains the GMF source
models. However, this plugin is not included in the helios release at
may I ask if you have been successful in generating the "diagram code" and the editors using 'org.eclipse.uml2.diagram.def'?
I spent two day, trying many different versions of Uml2Tools and Eclipse (including Helios and Uml2Tool 0.9.2) without success. I also tried following an old tutorial (GMF cookbook) step by step, but I cannot generate anything!
Vlad Varnica Messages: 546 Registered: July 2009 Location: Milton Keynes - UK
It will not work today because profiles are not transferable.
You can try EclipseUML Omondo and profiles will immediately work. Graphical DSL on the top of UML profiles mechanism is a glue which is specific and should be paid as an integration project.
My vision is not to recommend creating your own metamodel from EMF but the use of the standard UML metamodel (e.g. OMG standard) and add stereotypes on the top of it is the best solution. Once the stereotype has been added then the shape of the UML element is changed at diagram level. I mean that you can decide to have for example an interface like a square or a lollipop. This is the same model element but different graphical representation. This graphical mechanism could be extended to all UML elements and the use of stereotypes will create specific graphical DSL.
If UML doesn't contains the needed graphical information then you can add thos information directly in the metamodel such as a note, or constraint etc...It means that the internal UML2 metamodel mechanism is running the model validation (e.g. absolute marvelous technology) and any additional information would be used as internal model DSL. The shape mechanism would change the graphical design depending on stereotypes, notes etc.....