Especially the construction of an Eclipse wizards is more difficult than I estimated. It just catches exceptions without any feedback, just from time to time a “Event Loopback” occurs which is easy to track. Additionally all the magic SWT style number are weird. So, you can just instantiate a new Composite with
new Composite(parent, SWT.V_Scroll);and get a Composite with a vertival scrollbar. Sounds cool, isn’t it. But if you try to add several other composites as children of the scrollable, there is no scrolling at all. I just try to get it working.
In addition, there is no possibility to remove pages from a wizard, I temporally just monkey patch it, but I asked myself, if one should really only use constant pages, and just modify the contained composites. Another issue was the complete unchangeable order of pages, so I just added a public arraylist and redirect all accesses to the private pages of the supertype.
According EMF, it really do not fit in my mind, why one cannot inherit from data types. Especially EMF specific interfaces, which I think should be supported or at least been modeled in the Ecore model itself , are not available to inherit from.
Some nice idea for EMF would be an code synchronization plugin, which will kust update the models, if one change the parameter type of a method or just add a new attribute. Because the development process suffers from the frequent switch between code and model, just for keeping the model up to date.
Today, I just get an insight into the upcoming UML stencilset for the Oryx Editor (Oryx Project). It look great, nearly all concepts of UML get supported, but it was an hard manual matching against the UML meta model. Let’s think about a way to parse xmi meta models to stencilsets and vice versa, would be a powerful concept. I will just go on research on this topic.