Eclipse 3.x applications will continue to work in the foreseeable future but the API is frozen and will not receive any updates. Being able to incrementally update an application by migrating views allows developers to take advantage of injection and UI management through fragments.

It's possible to migrate code by directly replacing the user interface building blocks with explicit calls to code services, as shown in the first half of this chapter. However, this will result in a large amount of code being written, which may be counter-productive. Instead, a more Eclipse 4.x-based approach is to create a model fragment file and define the parts, commands, handlers, toolbars, view menus, and pop-up menus in the fragment.

The next chapter will look at styling Eclipse 4.x applications.