|Re: Diagram extensions behave differently [message #1226626 is a reply to message #1225883]
||Thu, 02 January 2014 08:33
| Maxime Porhel
Registered: July 2009
Le 31/12/2013 04:06, Michael Lukaszczyk a écrit :
> Hey there, (it´s me again ;)...)
> I noticed that a diagram extension that extends a diagram outside it´s
> own VSP scope behaves differently then it would be, if it would extend a
> diagram in it´s own VSP´s scope. I want to extend the basic ecore design
> editor "viewpoint:/org.eclipse.sirius.sample.ecore.design/Design" and
> provide an additional layer.
This an accepted construction.
The problem is, that all the container
> nodes appear twice now. But I just want to override a style for an
> existing container in the base layer.
Could you present the VSM structure you chose for that ? Addtional Layer
+ Node/ContainerMappingImport or AdditionalLayer + Node/ContainerMapping
or AdditionLayer + StyleCustomization ?
When I copy the ecore.odesign file
> to my own project and extend the local Design viewpoint I get my desired
> result. But I don´t want the additional dependency/redundancy in my
> project. I want to reuse the viewpoint from the plugin. Is this maybe a
> bug or is it supposed to be like this?
You should not have to copy the ecore.design in your project, and the
behavior should be the same with the extended VSM in plugins or in the
same project. With more details on your extension (structure, semantic
candidates expressions), I will maybe be able to explain what happens
and to answer you questions.
I mean, it´s still an extension,
> so it shouldn´t be like this, right?
Powered by FUDForum
. Page generated in 0.03645 seconds