Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse 4 » Making the e4 pojo programming model accessible from org.eclipse.ui extension points
Making the e4 pojo programming model accessible from org.eclipse.ui extension points [message #737036] Fri, 14 October 2011 11:40 Go to next message
Ralf Ebert is currently offline Ralf Ebert
Messages: 168
Registered: July 2009
Senior Member
Hi,

some weeks ago I filed feature request 356511 - Make pojo programming
model accessible from org.eclipse.ui extension points:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=356511

As of now I prefer the extension point model a lot more, conceptually
and especially in terms of the available tooling, to the application
model for the contracts that plug-ins of RCP applications make with the
platform. Thus I wanted to follow up on the feature request. Would you
consider extending the compatibility layer to allow to make usage of
new application model features at all? Would a contribution to allow
this be welcome? Any ideas on what a good distinctive criteria for an
old-style and a new-style class could be?

Greetings,

Ralf


--
Ralf Ebert
http://www.ralfebert.de/
Re: Making the e4 pojo programming model accessible from org.eclipse.ui extension points [message #737063 is a reply to message #737036] Fri, 14 October 2011 12:05 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5296
Registered: July 2009
Senior Member
Did you ever looked at my e4-bridge. It brings the e4 programming model
to Eclipse 3.x-style ViewParts/Editors

Tom

Am 14.10.11 17:40, schrieb Ralf Ebert:
> Hi,
>
> some weeks ago I filed feature request 356511 - Make pojo programming
> model accessible from org.eclipse.ui extension points:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=356511
>
> As of now I prefer the extension point model a lot more, conceptually
> and especially in terms of the available tooling, to the application
> model for the contracts that plug-ins of RCP applications make with the
> platform. Thus I wanted to follow up on the feature request. Would you
> consider extending the compatibility layer to allow to make usage of new
> application model features at all? Would a contribution to allow this be
> welcome? Any ideas on what a good distinctive criteria for an old-style
> and a new-style class could be?
>
> Greetings,
>
> Ralf
>
>
> --
> Ralf Ebert
> http://www.ralfebert.de/
>
Re: Making the e4 pojo programming model accessible from org.eclipse.ui extension points [message #737081 is a reply to message #737063] Fri, 14 October 2011 12:33 Go to previous message
Ralf Ebert is currently offline Ralf Ebert
Messages: 168
Registered: July 2009
Senior Member
Hi Tom,

thanks, but that's not what I am after, if I understand your approach
correctly. I'd like to continue using extensions and extension points
on the Eclipse 4.x runtime and still get some benefits of the
application model underneath, instead of staying on 3.x with backported
features of 4.x. Also I am trying to find out if such an approach could
be officially supported by the platform and doesn't have to be added on
top using extra utility plug-ins.

I think both e4-style classes (without base class and @Inject-support)
and old-style ViewPart classes could be supported by the extension
points in the compatibility layer without much effort. In the latter
case, the compatibility view class that's in between right now could be
dropped and the extension class could go into the application model
directly. As demonstrated via hack in the bug report. Any opinions on
that?

Greetings,

Ralf



On 2011-10-14 16:05:25 +0000, Tom Schindl <tom.schindl@bestsolution.at> said:

> Did you ever looked at my e4-bridge. It brings the e4 programming model
> to Eclipse 3.x-style ViewParts/Editors
>
> Tom
>
> Am 14.10.11 17:40, schrieb Ralf Ebert:
>> Hi,
>>
>> some weeks ago I filed feature request 356511 - Make pojo programming
>> model accessible from org.eclipse.ui extension points:
>>
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=356511
>>
>> As of now I prefer the extension point model a lot more, conceptually
>> and especially in terms of the available tooling, to the application
>> model for the contracts that plug-ins of RCP applications make with the
>> platform. Thus I wanted to follow up on the feature request. Would you
>> consider extending the compatibility layer to allow to make usage of new
>> application model features at all? Would a contribution to allow this be
>> welcome? Any ideas on what a good distinctive criteria for an old-style
>> and a new-style class could be?
>>
>> Greetings,
>>
>> Ralf
>>
>>
>> --
>> Ralf Ebert
>> http://www.ralfebert.de/
Previous Topic:Dropdown in Toolbar
Next Topic:Question regarding ESelectionService
Goto Forum:
  


Current Time: Tue Sep 02 15:06:07 EDT 2014

Powered by FUDForum. Page generated in 0.01656 seconds