| Different properties view? [message #1571912] |
Sun, 18 January 2015 18:09  |
Eclipse User |
|
|
|
Hi,
I just started to use Sirius to define a graphical editor for Odesign models themselves. It can be used to define nodes, edges and their styles for layers, to get a quicker visual feedback on how the (static) styles look like. It's available here:
https://github.com/Boereck/odesign-designer
But the editing experience suffers, because the graphical editor is not connected to the properties view of the "Viewpoint Specification Editor" (the default editor for .odesign models). Is there a possibility to make the graphical editor contribute the same UI to the properties view as the "Viewpoint Specification Editor"?
Thanks and best regards,
Max
|
|
|
|
|
| Re: Different properties view? [message #1577192 is a reply to message #1576788] |
Wed, 21 January 2015 14:17  |
| Eclipse User |
|
|
|
Hey Steve,
The properties view in the "Viewpoint Specification Editor" is actually pretty damn good, so I don't see the need to create an own one (at least for this, or other tree based editors).
I actually got very far in creating the designer for Odesign, It can already display and edit a lot, but the most severe thing is that it cannot really save.
Somehow I feel (without knowing the insides of the implementation of the Odesign meta model and surrounding technologies) that serializing a valid instance of that meta model should not be a difficult thing. I even can open an Odesign model with the "Sample Reflective Ecore Model Editor", make changes and save it again.
I can imagine that the "Viewpoint Specification Editor" and it's properties view have a lot of magic inside and it would be hard to re-use parts of it. So I could consider learning how to use EEF to create a properties view for my graphical editor. But as long as the graphical editor is not able to save, this is kind of pointless. The properties view for the "Viewpoint Specification Editor" is awesome (you fellas did a really great job!), so it does not need a replacement.
Cheers,
Max
|
|
|
|
| Re: Different properties view? [message #1587341 is a reply to message #1585820] |
Tue, 27 January 2015 04:30 |
| Eclipse User |
|
|
|
Hello,
We have some JUnit test where the ODesign is modified for the purpose of
the test, but in the common usage of Sirius it should not be modified
and needing saving. Especially, if the odesign is in the plugins.
You can try to override it but you can experience drawbacks in
performances and unstability.
Best regards,
Steve
Le 26/01/2015 14:58, Max Bureck a écrit :
> Hi,
>
> I debugged the Sirius code to determine why changes to .odesign files
> are not saved. In method
> org.eclipse.sirius.business.internal.session.danalysis.ResourceSaveDiagnose#isSaveable()
>
> There is an explicit check if a file to be saved is an Odesign model. If
> this is the case, the method returns false.
> I was not able to get in this state, without explicitly adding an
> Odesign model to an .aird file via the UI and then modify this. Are
> there situations where an Odesign model would actually be saved
> accidentally, if this check would be omitted?
>
> Thanks and best regards,
> Max
--
Steve Monnier - Obeo
Need professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
Powered by
FUDForum. Page generated in 0.10976 seconds
Home