Eclipse Community Forums: Graphiti » Alternative implementations of diagram meta model?

Help

Home

Home » Modeling » Graphiti » Alternative implementations of diagram meta model?

Show: Today's Messages :: Show Polls :: Message Navigator

Alternative implementations of diagram meta model? [message #563450]

Wed, 18 August 2010 14:51

Ken Wenzel

Messages: 51
Registered: July 2009

Member

Hello,

we're currently building a prototype which uses Graphiti in combination with http://komma.sourceforge.net/ to create graphical editors for system structures.

In addition to Graphiti's diagram data, our business objects are stored as RDF data in separate resources.

Since KOMMA enables the mapping between Java objects and RDF, it could also be possible to store the PictogramElements as RDF.
A prerequisite to do this is to remove all EMF specific code from the org.eclipse.graphiti.mm plugin and introduce some interfaces that encapsulate the notification and persistence logic.

Now the question is, will the Graphiti team support such developments in the future?

Best regards,

Ken

Report message to a moderator

Re: Alternative implementations of diagram meta model? [message #563521 is a reply to message #563450]

Thu, 19 August 2010 08:34

Tim Kaiser

Messages: 118
Registered: July 2009

Senior Member

I think you can achieve persistence as RDF through the implementation
of an appropriate EMF Resource. Just plug the resource into the framework and it should do what you want.
(You probably would need to overwrite DiagramEditor, DiagramEditorFactory, and DiagramEditorInput)
I am curious if such an approach would do?
Best, Tim

Report message to a moderator

Previous Topic:	Alternative implementations of diagram meta model?
Next Topic:	Use dependency injection instead of singletons for services

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 18:01:23 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter