|Which version of platform would you use for a new development? [message #530094]
||Wed, 28 April 2010 09:18
Registered: April 2010
I'm expecting to start a significant new project that will include an Eclipse RCP based UI.|
We need to decide which version of the platform to start development on, 3.5, 3.6 or e4.
Which version would you go for and why?
The factors I've been thinking about are:
* release schedule
* experience in the community
* support from tools (include Instantiations RCP Developer)
* learning curve for developers and availability of training material, tutorials and other learning resources
* ease and pace of development
* compatability of 3rd party plugins
I won't bias your answers by stating my thoughts.
|Re: Which version of platform would you use for a new development? [message #530482 is a reply to message #530094]
||Thu, 29 April 2010 14:19
| Paul Webster
Registered: July 2009
> I'm expecting to start a significant new project that will include an
> Eclipse RCP based UI.
> We need to decide which version of the platform to start development on,
> 3.5, 3.6 or e4.
> Which version would you go for and why?
I would start on 3.5.2 and switch to 3.6.0 when it is released end of
June 2010 (your own app delivery target dates permitting).
If there is functionality (or bug fixes) that are in 3.6 that you
already know you need, then you may as well start now with 3.6. 3.6 M7
should be released the end of this week, and 3.6 RC1 2 weeks later (3.6
is already pretty stable).
e4 is an incubator project that contains new technologies, some of which
will be included in Eclipse 4.0 (Early Adopter Release)  end of July
2010. From writing an RCP app perspective, it has an EMF backed
workbench model, giving a lot more flexibility over the lifecycle and
placement of parts. It also has support for Dependency Injection that
can be used when instantiating parts (amongst other things), based
loosely on JSR 330. There are other additions as well.
e4 *is* a good choice if you want to adopt these kinds of technologies
(some a little rough around the edges) and want to take advantage of
Eclipse RCP but don't expect to use most of the infrastructure that the
3.x org.eclipse.ui.workbench or org.eclipse.ui.ide provides. e4/4.0
will ship with a compatibility layer that will run API clean 3.x plugins
.... but then you wouldn't have access to the e4/4.0 capabilities anyway
:-) I think there are some other good reasons to move to e4, but I
can't think of them off hand.
 there are still ongoing discussions over the naming/positioning of
Eclipse 4.0 (Early Adopter Release)
Powered by FUDForum
. Page generated in 0.01464 seconds