Die Eclipse 4 Application Platform (e4) ist das Folge-Release von Eclipse RCP SDK. Eclipse 4 führt innovative Programmiertechniken ein, wie z.B. dependency injection, application model, annotations und CSS styling. Sie reduziert die Komplexität und den Aufwand bei der Entwicklung von Rich-Client-Anwendungen.
The countdown is on for Eclipse 4. For the upcoming Juno release, the core tooling components will build on the Eclipse SDK 4.2. This series will introduce the new concepts in the Eclipse 4 Application Platform, aka RCP 2.0. It is likely that most projects will use the compatibility layer initially, however, it is worthwhile […]
From the Application Model to the Implementation of Views. This tutorial series introduces the core concepts of the Eclipse 4 Application Platform, aka RCP 2.0. One of the key innovations of e4 is the separation between the application model and the implementation of the application’s parts, such as view. In the first part of this […]
In the previous parts of this tutorial series we described how to create an application model and link those elements to implementations. Until now we have only worked with one application model, however, Eclipse applications usually follow a modular design. In this part, we describe how to extend an existing application mode […]
In most of the programming examples provided so far, we implicitly used a further innovation of Eclipse 4: dependency injection (DI). DI plays a central role in Eclipse 4, reason enough to devote a whole tutorial to this. […]
This tutorial describes the most important annotations used in Eclipse 4. In Eclipse 4, views are POJOs, and methods can be named arbitrarily. Therefore, methods that need to be called by the framework at a certain point in time must be marked with corresponding annotations, e.g., @Focus. […]
This tutorial describes the general idea of Eclipse 4 platform services as well as the most important ones in detail. One of the key strengths of a framework such as Eclipse has always been the possibility of reusing of a lot of framework functionality. In Eclipse 4, these framework features have mostly be transferred into services, which provides much more flexibility. […]
This tutorial describes how to do a soft migration to the Eclipse 4 (e4) programming model. The basic goal of the tutorial is to enable development using the new concepts such as Dependency Injection and Annotations, but without first requiring a complete application migration.[…]