[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sapphire-dev] Sapphire usage of Graphiti in juno M5

Hi Michael,


Thanks for the heads-up. Sapphire 0.4 did ship with Graphiti based diagram editor. But in Sapphire 0.5 we’ve started replacing Graphiti based diagram editor with our in-house GEF based editor. The main reason is we don’t use EMF model. We have built our own Sapphire Model. Another reason is we need to maintain control and flexibility in the diagram editor to be consistent with the rest of Sapphire framework.






From: Wenz, Michael [mailto:michael.wenz@xxxxxxx]
Sent: Monday, January 30, 2012 9:14 AM
To: sapphire-dev@xxxxxxxxxxx
Subject: [sapphire-dev] Sapphire usage of Graphiti in juno M5


Hi all,


I just noticed that Sapphire uses Graphiti and is part of the Juno release train.


We (the Graphiti) team have done changes to the Graphiti DiagramEditor API for Juno M5 that will affect you. I noted these compile errors in the Graphiti related part of Sapphire caused by this change:

-          DiagramEditorFactory has been renamed to DiagramEditorInputFactory

-          DiagramEditor.getCurrentMouseLocation() has been removed as it was duplicate with getMouseLocation(); please use the latter

-          DiagramEditorInput does no longer take the editing domain and the Boolean flag disposeEditingDomain, simply remove them

-          The editing domain is no longer held by the input object, it can now be retrieved via the DiagramEditor


I’m not sure if you are taking part in M5, so this is a quick heads-up in case you do. Please let me know if you have questions.