Eclipse Community Forums: Eclipse 4 » Pure e4 Application with old UI extensions

Home » Eclipse Projects » Eclipse 4 » Pure e4 Application with old UI extensions (Support to reuse old plugins having UI extensions into E4 application based on specific Application Model [Not Legacy Application Model])

Pure e4 Application with old UI extensions [message #671517]

Wed, 18 May 2011 03:57

Eclipse User

A pure e4 application is designed and modeled using menu and toolbar. Now using "org.eclipse.ui.menus" extension point, two extensions are added:

1st for New Menu and Menu-Items,

2nd for Toolbar item by side of existing ones in the application model.

When the application is executed [No compat layer of e4 used like LegacyApplition.e4xmi], the extension of "org.eclipse.ui.menus" are not visible, also it is not added as part of application model under Windows tree-node in the model at runtime.

If this is not supported, Reusing old plugins based on extensions with pure e4 application will become impossible and those plugins will be required to be re-written which is not possible.

Is this feature is supported by some means?

Thanks,
Kunal

Re: Pure e4 Application with old UI extensions [message #671552 is a reply to message #671517]

Wed, 18 May 2011 05:45

Eclipse User

Am 18.05.11 09:57, schrieb Kunal:
> A pure e4 application is designed and modeled using menu and
> toolbar. Now using "org.eclipse.ui.menus" extension point,
> two extensions are added:
> 1st for New Menu and Menu-Items,
> 2nd for Toolbar item by side of existing ones in the
> application model.

Using org.eclipse.ui always means you need to use the compat layer!

>
> When the application is executed [No compat layer of e4 used
> like LegacyApplition.e4xmi], the extension of
> "org.eclipse.ui.menus" are not visible, also it is not
> added as part of application model under Windows tree-node
> in the model at runtime.

Correct without the compat layer no extension points are evaluated
(beside the e4-specific one!).

>
> If this is not supported, Reusing old plugins based on
> extensions with pure e4 application will become impossible
> and those plugins will be required to be re-written which is
> not possible.

Correct without the compat layer you can't use them.

>
> Is this feature is supported by some means?

Not out of the box that's exactly what the compat layer does! You can of
course write e.g. a model processor which consults the
org.eclipse.ui.menus-extension point and adds the model elements (you
could inspire yourself by looking at the compat layer code)

Tom

Re: Pure e4 Application with old UI extensions [message #671583 is a reply to message #671552]

Wed, 18 May 2011 08:05

Eclipse User

But normally, you should be able to activate the compatibility layer on top of 3.x components and so mix pure e4 based components and 3.x components without writing that model processor, isn't it?

Max

Re: Pure e4 Application with old UI extensions [message #671593 is a reply to message #671583]

Wed, 18 May 2011 08:12

Eclipse User

Yes to some extend you can do that.

The problem might be an ordering one because if you depend e.g. on a
perspective contributed through the old system to reference in something
coming from our new model contribution story this might cause problems.

I'm not yet sure if the compat layer or the model contributions are
processed first but Paul/Remy might be able to answer this.

Still in general you are right mixing in new e4 style components into an
environment where the compat layer is doing it's job might be possible.

Tom

Am 18.05.11 14:05, schrieb Maxime Jeanmart:
> But normally, you should be able to activate the
> compatibility layer on top of 3.x components and so mix
> pure e4 based components and 3.x components without writing
> that model processor, isn't it?
>
> Max
>

Re: Pure e4 Application with old UI extensions [message #671625 is a reply to message #671583]

Wed, 18 May 2011 10:11

Eclipse User

Right now we support 2 modes. 1) is a "pure Eclipse 4" RCP app, where we render the model, and provide model fragment and model processor extension points. 2) is Eclipse SDK 4.1, basically Eclipse 4 running the 3.x compatibility layer. The compat layer is what reads the 3.x extension points.

The longer term goal is to be able to load 3.x API consumers and write new stuff entirely using Eclipse 4 APIs. This will still involve using the compatibility layer, but hopefully with the lifecycle ordering corrected. i.e. launch an Eclipse 4 RCP app, and when contributions need 3.x APIs fire up the compat layer to provide access. This will hopefully be accomplished (or mostly done) in the 4.2 timeframe.

PW

Previous Topic:	Ressources tracking in E4
Next Topic:	Injection and Inheritance

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 12 02:10:36 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter