|Re: Xpand and Xtend2/Xtext [message #798277 is a reply to message #798256]
||Tue, 14 February 2012 13:28
| Karsten Thoms
Registered: July 2009
How does the old "components" in Xpand fit into Xtend2? Does it fit at all?
If you mean the Generator workflow component, there is a similar one in Xtext, which assumes that you have an Xtend class configured in the guice config that implements IGenerator. For Xtext based models this works quite out-of-the-box, and an appropriate workflow is generated for you. For other workflows you will have to provide a Guice Runtime Module and an implementation of ISetup to use this component. Or you write your own one deriving from AbstractWorkflowComponent2.
Is it at all possible to migrate the old solution to Xtend2?
Possible, of course. Automatic - no. This is a migration project. But you could translate Xpand to Xtend Rich Strings and Xtend1 functions to Xtend2 methods quite straight forward.
Is the development of Xpand stopped in favour of Xtend2?
More or less. Xpand will be maintained for some time, but development effort is put into Xtend2.
Is it worth it?
Yes. The tooling for Xtend is now already much better than for Xpand. Further, Xtend2 compiles to Java. The resulting code has just minimal runtime dependencies and is hell fast. Xpand is an interpreted approach and naturally slower. However, code generation performance is usually not a direct problem until reaching large scale models or generators.
There are also some gaps that Xtend has against Xpand and probably does not close in mid-term. One prominent example are the extensible type systems, especially the UML typesystem. When working with profiled UML models Xpand is definetely the best approach so far.
Need professional support for Xtext, Xpand, EMF?
Go to: http://xtext.itemis.com
Twitter : @kthoms
Blog : www.karsten-thoms.de
Powered by FUDForum
. Page generated in 0.17960 seconds