Last Friday we (eclipse.org) officially released the M5 of the Helios release train. Xtext, being part of the train, got a couple of new & noteworthy features we (Xtext team) are very happy (and sort of proud) with.
I'm personally most excited about the new builder infrastructure, which allows to revalidate, index and build any kind of EMF resource. Some of the new features we added in M5 demonstrate the huge potential of that builder infrastructure. My favorite is the open element dialog, which I use frequently. Besides that we also added a couple of other features like, auto editing, bracket matching and styled label providers. Our new & noteworthy document shows the most important feature additions using screenshots and small screencasts (we hope you like it).
During M6 we will add some features as well as doing the regular bug fixes. Also we will do a major rename refactoring (actually it is already done), so you might face some migration efforts when you upgrade. For M7 we are going to focus on performance improvements and further bug fixing. Documentation, tutorials and migration guide will be worked on during the RC phase. In parallel we're working on a new general purpose language developed in Xtext. It is meant to be some kind of library. Everyone should be able to reuse, adapt and extend that language within her own Xtext languages. That language won't be released with Helios, but as it is open-source you might be able to check it out by that time.
Btw.:
Have you already voted for the Eclipse Community Awards?
No? Go here.
Hi Sven,
ReplyDeletethanks a lot for putting so much effort into xtext. I tried to get some of the examples running, when I download the latest itemis bundle and create e.g. the domainmodel example from the wizard, I have lots of unresolved referenced. Even when I fix them in the manifest file, the code generation generates code that cannot run. Same for the other examples. And I have not found the correct location on CVS. The ones I checked out are all marked for deletion (from :pserver:anonymous@dev.eclipse.org:/cvsroot/modeling).
Hope you do not mind that unofficial bug report :-)
Markus
yes, there are some minor configuration problems in the example. We'll make sure that they are fixed in M6.
ReplyDeleteAbout rename refactoring. I guess you are talking about an internal rename refactoring. I am wondering about generated rename refactoring or unused definition warnings. This should be pretty easy to implement due to the find references being implemented. Is anyone working on that?
ReplyDeleteYes, we're working on generic rename refactoring.
ReplyDeleteGood to hear about the rename refactoring developments. Is there a chance that this might make the Helios release or will it be for a subsequent release do you think?
ReplyDelete@Chris: No, we have API freeze and want to take the time to fix bugs, write documentation and do general polishing. We have a prototype and might be able to make it available early after the release, but attached with a big disclaimer, etc. ;-).
ReplyDelete