My use case is from an IDE integrator perspective. We have build lots of tooling orbiting the IDE. We want to switch to the E4PM while still fully integrating with the IDE. I think this requires the following:
Pojo Extensions
Views
Editors
Preference Pages (mb Markus)
Handlers (mb Lars)
I think we should provide pojo extension points first for stuff that is unlikely to be ported to the model in the near future (e.g. preference pages). I can define an E4 view right now in a model and would much rather define it there than in plugin.xml (provided that the model can be imported into the IDE). This means that the plugin.xml will only be used for things that cannot be defined in the model.
Categories
View
Wizard (new/import/export)
Shortcuts (perspective/wizards)
Or a service to register my pojo to these categories.
Bridges
We also need a way to let old communicate with new:
Selection service
State persistence (IMemento vs Model) (not sure if this already works OOTB)
Allow to install Models and Fragments into the IDE
Finally a supported enablement to load E4 (fragment) models into the IDE would be really cool.
Regards,
Wim
