Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse 4 » Pros and Cons for starting a e4 project
Pros and Cons for starting a e4 project [message #574812] Sun, 18 April 2010 21:51 Go to next message
Obermaier Dominik is currently offline Obermaier DominikFriend
Messages: 2
Registered: April 2010
Location: Germany
Junior Member
Hi,

I absolutely like the new features of the Eclipse e4 project. There are some great improvements, which could help me a lot for my new project. I would love to hear some recommendations from some more experienced RCP and Plugin developers, my last RCP project was a year ago, so I'm going through the learning curve again (of course faster, I hope ;) ).

Here is what I want to do: I want to develop a toolset, which I want to use as Eclipse Plugins and a RCP Application, which should be the Standalone version of this plugins. The features and API freeze of e4 is almost there and I'm very interested in using e4.

Would you recommend to start a new project (First Alpha release should be December 2010) with e4? The toolset I want to develop is needed before, so this plugins have to work with Eclipse 3.5/6, but I would like to build the RCP Application upon the e4 framework.

Of course I don't want to write the whole code for two platforms, but I don't want to depend on an "old" framework, because when my RCP should be released, I think the 3.* Versions of Eclipse could be too old and everyone else uses e4 ;)

Is it possible to develop the Plugins for 3.5/6 and then move later to e4 without rewriting the whole code? Of course I would like it much more to develop my plugins for e4 instead of 3.* but I don't think this is a good idea, because I need the plugins I develop for developing other things => I'm not sure to use e4 as soon as it will be released as main IDE, most of the plugins I need would be not available at the beginning of the "e4 era" ;)

What do you think or recommend? Is it to early to use e4 in production? I would really love to read experiences and recommendations :)

Sincerely,

Dominik
Re: Pros and Cons for starting a e4 project [message #574932 is a reply to message #574812] Tue, 20 April 2010 16:11 Go to previous messageGo to next message
Erdal Karaca is currently offline Erdal KaracaFriend
Messages: 853
Registered: July 2009
Senior Member
e4 > R35

That means that you cannot run an eclipse 3.5/3.6 (R35) plugin in e4 unless you add the compatibility layer (c) to e4:

e4 + c >= R35

I think you will have to compile against R35. This will run in e4+c.
Once you do not need (to support) R35 anymore, you can remove c and migrate to pure e4, i.e resolve all compile errors :)
Re: Pros and Cons for starting a e4 project [message #574957 is a reply to message #574812] Tue, 20 April 2010 16:46 Go to previous message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6520
Registered: July 2009
Senior Member
Hi Dominik,

I think you can write "singlesource" plugins that run on 3.x and e4
without the compat layer.

We are already have an example in e4 which shows how to implement it
because e4 uses very very loosely coupled bundles and enforces a
Service-Oriented Programming style (it's not 100% done yet and we'll
improve the structure to get used as THE example for singlesourcing e4
and 3.x).

The example I'm talking about is the Model-Editor I'm developing -
todays there's only one small hack needed to run it in 3.6 which we are
trying to address in https://bugs.eclipse.org/bugs/show_bug.cgi?id=309593


Tom

Am 18.04.10 23:51, schrieb Obermaier Dominik:
> Hi,
>
> I absolutely like the new features of the Eclipse e4 project. There are
> some great improvements, which could help me a lot for my new project. I
> would love to hear some recommendations from some more experienced RCP
> and Plugin developers, my last RCP project was a year ago, so I'm going
> through the learning curve again (of course faster, I hope ;) ).
>
> Here is what I want to do: I want to develop a toolset, which I want to
> use as Eclipse Plugins and a RCP Application, which should be the
> Standalone version of this plugins. The features and API freeze of e4 is
> almost there and I'm very interested in using e4.
>
> Would you recommend to start a new project (First Alpha release should
> be December 2010) with e4? The toolset I want to develop is needed
> before, so this plugins have to work with Eclipse 3.5/6, but I would
> like to build the RCP Application upon the e4 framework.
> Of course I don't want to write the whole code for two platforms, but I
> don't want to depend on an "old" framework, because when my RCP should
> be released, I think the 3.* Versions of Eclipse could be too old and
> everyone else uses e4 ;)
>
> Is it possible to develop the Plugins for 3.5/6 and then move later to
> e4 without rewriting the whole code? Of course I would like it much more
> to develop my plugins for e4 instead of 3.* but I don't think this is a
> good idea, because I need the plugins I develop for developing other
> things => I'm not sure to use e4 as soon as it will be released as main
> IDE, most of the plugins I need would be not available at the beginning
> of the "e4 era" ;)
>
> What do you think or recommend? Is it to early to use e4 in production?
> I would really love to read experiences and recommendations :)
>
> Sincerely,
>
> Dominik
Previous Topic:Pros and Cons for starting a e4 project
Next Topic:XWT. Problem with Form background.
Goto Forum:
  


Current Time: Fri Jan 24 04:48:17 GMT 2020

Powered by FUDForum. Page generated in 0.01680 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top