|Re: Using File oriented editors and package explorer in e4 [message #1727658 is a reply to message #1727625]
||Thu, 24 March 2016 20:39
| Thomas Schindl
Registered: July 2009
e4 lacks the notion of (text)-editor framework. e(fx)clipse has core
infrastructure that can be used even in an SWT context.
I wrote a proof-of-concept for SWT some weeks ago -
By default the framework will always open the same Text-Editor and
reconfigures it but you can contribute your own OSGi-Service to:
* reconfigure which Editor-Class is used (EditorClassURLProvider)
* reconfigure how the editor is opened from an e4 model point of
I think the concepts we have are superior to the ones you see in e3 and
they are not a direct downport from the e3 APIs to work in e4 world -
they use the power of e4 DI and OSGi-Services to give you better code
reuseage, less framework dependency and many many other goodies.
On 24.03.16 15:13, Thomas Elskens wrote:
> I was wondering: when reading tutorials on migration e3 -> e4, I never
> come across the discussion of a quite basic use case: the one were we
> register an Editor to open/edit/... a file which is opened/double
> clicked in the package explorer.
> With Eclipse 3 API, this is very easily achieved by associating a file
> extension to a given type of Editor, the platform does the rest.
> I suppose the answer to my question is that for the time being there is
> no (reasonably productive) way to achieve the same behavior with e4 API,
> but perhaps I somehow overlook something ... ?
> Thanks for any input,
> Thomas Elskens
Powered by FUDForum
. Page generated in 0.02157 seconds