Hi,
The graphical syntax for TUs was not supported / enabled in the last
release. Therefore, the only thing that needs to be translated
correctly are the rules and amalgamation units. For these, no
problems will occur. So adapting the graphical models is really as
simple as I wrote in my previous e-mail.
cheers,
christian
On 01/13/2012 04:58 PM, Stefan Jurack wrote:
In cases where only amalgamation units (and other unchanged parts)
need to be migrated, this might work. I.e., in cases where the
visual representation remains. However, in terms of Counted units
which are translated into a Loop unit or a Sequential unit (with
other stuff in it), new graphical elements need to be created and
others needs to be deleted....with all its implications. Possible
but pretty tricky.
Am 13.01.2012 16:26, schrieb Christian Krause:
Ok, here is a rough version:
ResourceSet resourceSet = new ResourceSetImpl();
// Load ALL *.henshin and *.henshin_diagram files now:
resourceSet.getResource(henshinURI, true);
resourceSet.getResource(henshinDiagramURI, true);
// ...
// Now migrate the models. Keep track of the newly
created elements!
Map<EObject,EObject> old2new = new
HashMap<EObject,EObject>();
// do the conversion...
// After the models are replaced, updates the diagrams:
for (Resource resource : resourceSet.getResources()) {
for (EObject root : resource.getContents()) {
if (root instanceof Diagram) {
updateViews((Diagram) root, old2new);
}
}
}
// Save all resources:
for (Resource resource : resourceSet.getResources()) {
resource.save(null);
}
/*
* Recursively update view elements.
*/
private static void updateViews(View view,
Map<EObject,EObject> old2new) {
if (view.getElement()!=null) {
EObject newElem = old2new.get(view.getElement());
if (newElem!=null) {
view.setElement(newElem);
}
}
for (Object child : view.getChildren()) {
updateViews((View) child, old2new);
}
}
The notation package (for View and Diagram classes) is located
in org.eclipse.gmf.runtime.notation;
Let me know if you need more info / help or testing...
cheers,
christian
On 01/13/2012 01:25 PM, Stefan Jurack wrote:
I still have serious doubts that the migration of the diagram file works
properly in general ... at least without putting extraordinary effort in
that!! We'd better concentrate on other issues such as bringing Henshin
into an overall consistent state.
Am 13.01.2012 12:47, schrieb Riegerf@xxxxxxxxxxxxxxxxxxxxxxx:
Hi Christian,
Quoting Christian Krause <henshin.ck@xxxxxxxxx>:
can you please give us an estimate when you think a first version of
the migration tool is ready for testing?
a first version was already done and converted the henshin test rules
just fine. (The version in the SVN might be an intermediate version
and might thus not work, though.) I'm currently working on
implementing the latest model change, which seems to be done right
now, so the new and updated version should be ready later today (and
working) in case I don't find any obvious errors.
The next step is converting the graphical editor files. Do you have
any specification on their structure or file format? (Both old and
(probably?) new versions).
Please also take a look at the henshin 2011 model I'm using for my
transformation and check its correctness.
Felix
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/henshin-dev
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/henshin-dev
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/henshin-dev
_______________________________________________
henshin-dev mailing list
henshin-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/henshin-dev
|
