Migration strategies [message #847761] |
Tue, 17 April 2012 16:22 |
Axel Guckelsberger Messages: 354 Registered: July 2009 |
Senior Member |
|
|
Hi all,
I have been reading many articles about MWE2, Xtext, Xbase and Xtend2. Now I want to start migrating an existing RCP project based on EMF, GMF, Xpand, Xtend and oAW.
My problem is that I have a few difficulties when it comes to the right order of implementation.
I wanted to start with the generator as this is probably going to become the easiest part. Introducing Xtend seems to require an existing Xtext grammar though. Therefore defining the grammar by deriving it from the existing ecore metamodel should be the first step, right?
Although I have seen that it is possible to derive a grammar automatically, a manual reimplementation would be preferable, wouldn't it? Later the meta model is then generated from the Xtext grammar, so the current metamodels are going to be deleted then?
And where is the place for Xcore in this scenario? If I need a Xtext grammar, can Xcore still be of help? Or is this only intended for projects where Xtext is not involved on the application side?
Thanks in advance for your help!
|
|
|
Re: Migration strategies [message #847854 is a reply to message #847761] |
Tue, 17 April 2012 18:19 |
|
Hi,
Xcore is a DSL that replaces the ecore tree editor. => you could use it to define you metamodel.
since you have already one you could use it => that you dont need Xcore.
you have already a metamodel => you do not have to let Xtext derive one
Xtend does not need an Xtext Grammar, it needs only emf java classes => a genmodel + generate model code
will do the trick => since you use GMF this is already done.
You can generate with Xpand too
=> the first step would be to define a grammar for your existing metamodel.
~Christian
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
Re: Migration strategies [message #847858 is a reply to message #847761] |
Tue, 17 April 2012 18:19 |
|
Hi,
Xcore is a DSL that replaces the ecore tree editor. => you could use it to define you metamodel.
since you have already one you could use it => that you dont need Xcore.
you have already a metamodel => you do not have to let Xtext derive one
Xtend does not need an Xtext Grammar, it needs only emf java classes => a genmodel + generate model code
will do the trick => since you use GMF this is already done.
You can generate with Xpand too
=> the first step would be to define a grammar for your existing metamodel.
~Christian
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03376 seconds