Hi Erdal, We have been working on this as well a while ago. If you want you can take a look at the unfinished solutions here:
https://github.com/E4Examples/importworkbenchbridge https://git.eclipse.org/r/#/c/21111/ Bug 376486 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=376486> - IDE not extendable via fragments or processors <https://github.com/E4Examples/importworkbenchbridge> On Fri, Jan 6, 2017 at 12:08 PM, Erdal Karaca <[email protected]> wrote: > Hi devs, > The ModelAssembler only merges fragments into the app model if it can find > the parent to extend. If we have an E4 app with compat layer AND the > fragments are extending elements generated within E3 workbench > intitialization phase, the fragments are not merged. > > I have experimented a bit with the internals of > E4Application/ModelAssembler to load E4 fragments into the application > model after the compat layer has loaded the E3 workbench. > The result is that it seems to be possible to merge E4 fragments into E3 > API driven products, i.e. E4 with compat layer. > > Now, I am not sure if I am missing some obvious points using this approach > as seemed to work quite smoothly. > As the various renderes listen to model changes, I expect them to handle > dynamically added elements properly. > Do you have or know of any concerns? > > _______________________________________________ > e4-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/e4-dev >
_______________________________________________ e4-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/e4-dev
