There are use cases, where you run an e4 application, but some parts are not directly able to access the IEclipseContext. Especially if a framework is single sourced between e4 and 3.x As an example I had the following case: An application provides a extension mechnism which action should be triggered on double clicking an element. The extension point allows to implement a simple interface (Opener):
open(Object object) In case of 3.x I want to open an editor by default. In case of e4, I want to open a Part. As the core does not know about e4, I don't have any IEclipseContext in the e4 Opener. I can therefore not directly retrieve an EPartService. Cheers Jonas Am 23.01.2014 14:58, schrieb Paul Webster: > Hi Wim, > > On Thu, Jan 23, 2014 at 6:16 AM, Wim Jongman <wim.jong...@gmail.com > <mailto:wim.jong...@gmail.com>> wrote: > > > Well, it is not my current use case... But yes. I was thinking > about headless applications (e.g. all Eclipse RT related stuff) > with the model and the DI framework. So it would be nice if I > could get a hold of these services from outside of the > org.eclipse.ui realm. > > > In that case whoever wrote the headless app would have been > responsible for creating the Eclipse4 application and model and > runtime contexts (the renderers create these when using > E4Application), and you would have to negotiate with them on how to > access the model root and appropriate IEclipseContext. > > PW > > -- > Paul Webster > Hi floor. Make me a sammich! - GIR > > > _______________________________________________ > e4-dev mailing list > e4-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list e4-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/e4-dev
