Community
Participate
Working Groups
I’m working on my diploma project for the University of Applied Sciences in Biel (Switzerland) and I’ve been working with the EMF/JET to generate editors for models based on xsd. As expected it worked great for the generation of eclipse editor plugins, but when it came to generation of code for completely different purposes I had to notice, that the generation was hardcoded and not really adaptable. It only is possible to change the templates for the artifacts to be generated. Wouldn’t it be possible to let the whole GenModel follow the Visitor/Visitable pattern? What actually is generated would be implemented in Visitors visiting the GenModel. E.g for the generation of Eclipse editor plugins based on a GenModel there would be a specific EclipseEditorVisitor which would be packaged as an extension point to the GenModel plugin. In order to generate completely different artifacts for the GenModel it’d be enough to implement a GenModelVisitor and package it as a plugin providing an extension point to the GenModel plugin.
Pawel, I'll return this as a duplicate of the feature request we already have open to track this planned item. We'll solicit your feedback as we make progress in the design. *** This bug has been marked as a duplicate of 75925 ***
