Am 16.05.11 09:43, schrieb Mike Moor:
> i'm invited to a meeting where they want to decide if we use
> eclipse 3.x or eclipse 4 for new projects and if we should
> migrate the existing 3.x applications (about 30
> applications) to eclipse 4.
> what is your opinion?
> i would prefer eclipse 4 for new projects and leave the
> existing ones on eclipse 3.x.
the compat layer should allow you to run your applications in 4.x
and togetehr with the forward compat layer you can refactor it step by step.
I plan to write a tutorial soon about and gave a talk about it at
Eclipse Con 2011 . I'll hopefully be able to upload the sources to my
git repo soon.
> what are the main eclipse 4 advantages compared to eclipse
* the new programming model
* better control over L&F going even so far to replace widgets and even
the widget technology
* the workbench model which gives you complete control of your application
> why should one use eclipse 4 and not eclipse 3.x?
.... because it is going to be to main area of innovation in the years to
Am 19.05.11 13:41, schrieb Mike Moor:
> Thanks Tom
> It looks like I was successful.
> We start our first Eclipse 4 based application project in june.
> Since I am the only one who has a little experience with e4 there is an
> other question:
> Do you know an Eclipse 4 training?
> Or even better a trainer who would give a german inhouse training in
Well I'm Austrian so German is my mother tongue and my company offeres
Services around Eclipse Technologies (RCP, Eclipse 4.x,
EMF(-Databinding), Nebula, to name some) from Inhouse Trainings,
Consulting, Payed Coding (e.g. extension of Nebula-Widgets)... ;-)
Paul Webster Messages: 6859 Registered: July 2009 Location: Ottawa
I'll just add that even we are in the process of migrating to Eclipse 4
As part of the Eclipse 4 work, we've only migrated a few services to the Eclipse 4 level. There are still a lot of services used by 3.x RCP apps that live in the 4.2 Workbench (previously called the compatibility layer). Things like Preferences, all the wizards, standard sets of menus and actions, etc, all still live in the 4.2 workbench.
So while I encourage anybody that can use Eclipse 4 to take advantage of it, I wouldn't suggest moving any existing products to Eclipse 4 unless it wasn't consuming a lot of Workbench services *and* it could take advantage of the model or DI technologies.
That's not to say that 3.x RCP apps can't move up to build and run on Eclipse 4.2. With slight modifications they could start taking advantage of the CSS, which has stable API at the SWT level.