Duration: 1:00:47

1,217 views

9

At the last EclipseCon Europe 2012 I came to the conclusion: Eclipse 4 is mature enough to try a migration of the 3.x application OpenChrom® to e4. Meanhwile, OpenChrom consists of over 65 plug-ins containing several views and different perspectives. The concept to have POJOs for parts (views and editors) using dependency injection thrilled me. Thus, I read a lot of tutorials and books and eventually started with the migration in November 2012. By end of December, I felt that it was the dumbest decision I've ever made. Nothing, really nothing worked anymore and I've discovered a lot of bottlenecks that were not obvious before. But going back was no option. Hence, I was under a "certain" pressure to find solutions for the problems. By the way, it was horrible. Finally, after 8 month of hard work, I'm happy to offer a new release of OpenChrom 0.8.0 "Dempster", based completely on Eclipse 4.3 "Kepler". In this talk I would like to present solutions and answers for the following issues and questions:

Shall I run the application in the compatibility mode?
How to include the 3.x editor in a 4.x application?
Which views/wizards/dialogs are not available natively in e4?
What is about the preferences dialog?
Is there a native perspective/view switcher?
Can I reuse the properties view?
In summary, I would like to share the knowledge with you that I've made with the migration to e4. Furthermore, I would like to give some hints how to start with a migration. This may help you to avoid stepping into the same pitfalls as I've experienced.

Shake that FUD; How to migrate your Eclipse 3 legacy code to Eclipse 4, Lars Vogel, Wim Jongman

We will present an existing Eclipse 3 application that has been converted to Eclipse 4. We will use your existing 3.x expertise to show the new way of working. Then we will analyze the conversion of the old application to Eclipse 4. Step by Step.

You have heard about the model based Application Platform, Dependency Injection, the Rendering Engine and all that. You don't know exactly how it works yet but it sounds really cool and useful.

Your biggest concern at the moment is what to do with your old code. Can you keep using it as it is? Do you need to do a major code conversion? Is it just as rich as the old RCP? What if you just do plug-in development or have an RCP application that embeds a lot of platform code, like editors or the debugger?

Your fear is that your current code base will be useless when Eclipse 3 API will no longer be supported.
You are uncertain that it is possible to get your code to Eclipse 4 in a reasonable way.
You have doubt that the new way of working can be adopted by you without major hassle.

We will present an existing Eclipse 3 application that has been converted to Eclipse 4. We will use your existing 3.x expertise to show the new way of working. Then we will analyze the conversion of the old application to Eclipse 4. Step by Step.