+1 from me as well on adding the wrapper classes into the platform for 4.3.
Even for those starting fresh with RCP there are cases where a pure e4 implementation is not possible. Many RCP applications incorporate other Eclipse components that have not yet been converted (CNF, GMF/Graphiti, etc.) My suggestion to those teams is to use the wrapper classes, and it would be great if they were easier to incorporate.
Another option would be to allow putting POJOs directly into view, editor, and handler extensions and then creating the DI instances on the fly. Not completely sure if this is possible, but it would eliminate a lot of boilerplate wrapper subclasses and keep the DI classes out of the API.
Regards,
--- Patrick
This model is not meant to be used by starters. They can skip this completely. However, there is a huge installed base that wants to move forward with E4 but cannot do it because of the current inability to mix the two programming models. At the moment it can be used but if it is not officially supported and documented by platform then it will be considered a hack and people will keep on running their complete rcp in compatibility mode.
Not being able to "officially" run in mixed mode will severely hinder the adoption of E4.
Regards,
Wim
_______________________________________________ e4-dev mailing list e4-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/e4-dev
|