| persisting diagrams and palette [message #184881] |
Wed, 30 April 2008 10:18  |
Eclipse User |
|
|
|
hi there. I'm doing some tests with the experimental sdk in order to
achieve the visual ID preservation when adding a new widget to the ecore
model and re-generating all the rest of the models. It seems to work as
you do very little changes on gmftool or gmfgraph..
But when you add a new entire EObject to the root of the .ecore, delete
and regenerate the genmodel, add the needed tree structure portion to the
gmftool and gmfgraph... recombine alltogether, delete the .diagram, .edit
etc code folders and regenerate everything... you get a new palette with
the new component ready to work, but you lose the capability to open old
diagrams, those you've made with the previous palette version.
Instead, if I don't delete that much code, and try to modify only the tree
structures of ecore, gmftool gmfmap, gmfgraph "after" the gmfmap point of
the process... Then happens that the new widget does not appear on the
palette, but you can open old diagrams.
How can I achieve both of these features? I mean adding new components to
the palette(and modify their values in the model) without destroying the
visualIDs *and* being able to open old diagram files?
I need this feature because in our production, everytime we modify our
designer (made with gmf of course) to add a new feature all the previous
versions of the output files are no longer compatible, and we have to lose
several hours struggling on manually change the visualIDs.
Thanks in advance
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05177 seconds
Home