Eclipse Community Forums: Graphiti » Add Feature Implementation Exposed In Serialization & Legacy Diagrams

Home » Modeling » Graphiti » Add Feature Implementation Exposed In Serialization & Legacy Diagrams

Add Feature Implementation Exposed In Serialization & Legacy Diagrams [message #658704]

Wed, 09 March 2011 09:43

Eclipse User

The serialization of a Graphiti diagram exposes the implementation of its add features in its serialization. When a tool is developed using Graphiti and end users create diagrams they will develop a body of work to which they are pretty attached. Has anyone developed a strategy for the eventual moment when a version of this theoretical tool ships and it changes the implementation of the add features either to fix a bug or to enhance the display of its graphical elements?

The user's older diagrams will likely no longer be compatible. The domain model didn't change its version and the Graphiti model didn't change either. It's the add feature implementation and the features dependent upon that structure that have changed. Do we need to be supplying a version number on each of our root shapes so that we can detect old versions and upgrade them?

Re: Add Feature Implementation Exposed In Serialization & Legacy Diagrams [message #658718 is a reply to message #658704]

Wed, 09 March 2011 10:36

Eclipse User

Rhett,

You are quite right. We have not solved this problem yet, but we do mark all shapes in the Graphiti model using properties. This way you can identify which shapes are added by which add feature. Using this information you should be able to convert "old" diagrams to "new" diagrams.

Still quite some work is needed to make this actually work.

Jos

Previous Topic:	Reflecting Connection source/target change from diagram to business objects
Next Topic:	Create Automatically a model from EMF

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 04 14:37:03 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter