Can a Sirius modeler be available as plug-ins ? [message #1391190] |
Mon, 30 June 2014 15:15 |
Thomas Muller Messages: 9 Registered: September 2011 |
Junior Member |
|
|
Hi all,
first of all, congratulations to the OBEO team who developped Sirius. This is really a great tool!
I was using it to check differences with GMF which I've used until now.
In a current industrial project, I need to define a diagram editor and customize the figures, the anchors of bordered nodes, etc., and moreover, I don't want my Eclipse app users to edit this modeler.
Is it possible to export my modeler as a plug-in as it can be done in the regular GMF world ?
Best regards,
Thomas
[Updated on: Mon, 30 June 2014 15:28] Report message to a moderator
|
|
|
Re: Can a Sirius modeler be available as plug-ins ? [message #1391659 is a reply to message #1391190] |
Tue, 01 July 2014 08:08 |
Thomas Muller Messages: 9 Registered: September 2011 |
Junior Member |
|
|
Ok... I think I can partially answer to myself, but please add some comments if I'm wrong.
After reading the whole available documentation, I've realized that my question is not well formulated.
Indeed, it's not Sirius philosophy to get some java code that is later customized (GMF style). Instead Sirius provides the user with a declarative way to get a "runtime available" diagram editor (among other types).
My question would rather be: "How can one get the same level of graphical customisation as what one could get after having tuned the GMF generated code?".
Then:
1. To make the diagram editor available in your target RCP or Eclipse App: you just have to ship your Viewpoint Specification Project as a plug-in of your product which will also include its dependencies.
2. To get the level of customization for figures that you can reach with using the old GMF's way, you have to contribute to "org.eclipse.gmf.runtime.diagram.ui.editpartProviders" and "org.eclipse.sirius.diagram.ui.styleConfigurationProvider".
Is that correct? Is there any available documentation on this topic?
Regards,
Thomas
[Updated on: Tue, 01 July 2014 08:09] Report message to a moderator
|
|
|
|
Re: Can a Sirius modeler be available as plug-ins ? [message #1391678 is a reply to message #1391659] |
Tue, 01 July 2014 08:37 |
|
Hi Thomas,
Thank you for your feedback.
Concerning the second point, it depends on what kind of customization
you want to do. If you want to extend an existing modeler (like styles
or mappings) you can use the Sirius declarative mechanisms:
http://www.eclipse.org/sirius/doc/specifier/diagrams/Diagrams.html#extensibility
http://www.eclipse.org/sirius/doc/specifier/diagrams/Diagrams.html#customization
Concerning more complex customizations, (like extend existing EditParts
or Figures for instance) you can use the classic GMF extensible API.
Regards,
Florian
On 07/01/2014 10:08 AM, Thomas Muller wrote:
> Ok... I this I can partially answer to myself, but please add some
> comments if I'm wrong.
>
> After reading the whole available documentation, I've realized that my
> question is well formulated.
> Indeed, it's not Sirius philosophy to get some java code that is later
> customized (GMF style). Instead Sirius provides the user with a
> declarative way to get a "runtime available" diagram editor (among other
> types).
>
> My question would rather be: "How can one get the same level of
> graphical customisation as what one could get after having tuned the GMF
> generated code?".
>
> Then:
>
> 1. To make the diagram editor available in your target RCP or Eclipse
> App: you just have to ship your Viewpoint Specification Project as a
> plug-in of your product which will also include its dependencies.
>
> 2. To get the level of customization for figures that you can reach with
> using the old GMF's way, you have to contribute to
> "org.eclipse.gmf.runtime.diagram.ui.editpartProviders" and
> "org.eclipse.sirius.diagram.ui.styleConfigurationProvider".
> Is that correct? Is there any available documentation on this topic?
>
> Regards,
>
> Thomas
>
>
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03692 seconds