|Re: New RCP / Integration into legacy RCP / Which approach? [message #904525 is a reply to message #904430]
||Tue, 28 August 2012 15:51
| Matthias Gsteu
Registered: August 2012
Thanks for the replies so far.|
The new RCP will be rather view oriented than "input oriented". There will be some things the user has to configure but the main part is monitoring of data (with user interaction).
I'm sure that the new application itself would work quite well with e4, even if I had to implement my own navigator. But the integration into our old RCP would give some headaches I think.
As far as I know, the compatibility layer only enables us to bring our old ViewParts which are defined as extensions into the new application model.
But I would end up having a new E4 based RCP which should be integrated into an old one that runs in compat. mode.
And I have often read that mixing is not supported very well. What does that mean? Are there some hidden bugs?
Furthermore I was not able to contribute a Part via a Model Fragment into the existing (LegacyIDE) application model when running in compat. mode up to now. Is this one of the cases that is not supported very well?
The answer does not seem to be so simple - at least for me
Which application do you mean? The new one or the old one?
What do you mean with "you can't easily do..."? For me it means that it works, but not straight-forward.
Just to get you right: let's say I'm done with a new, pure E4 application. It has its own application model which defines Commands, Handlers, Bindings, Menus, a Perspective Stack with a Perspective and some PartStacks with their Parts.
The parts are implemented in the new way: POJO's with DI (@PostConstruct, and so on...)
In the meantime the old RCP runs on top of E4 in compatibility mode. Is it now possible to integrate the perspective with all its children from the new E4 application into the old one? Of course this should also work with the commands and handlers and so on.
I still can't get that...
Thank you guys a lot
Powered by FUDForum
. Page generated in 0.02973 seconds