Skip to main content
Jump to: navigation, search


< Eclipse4‎ | KnownIssues
Revision as of 11:37, 15 July 2010 by Susan (Talk | contribs) (Missing API/Developer functionality)

The Eclipse SDK 4.0 Early Adopter release is not intended to replace the Eclipse 3.6 SDK for most SDK end-users. Its primary focus is to allow developers of other Eclipse projects and plug-ins to prepare for a future Eclipse simultaneous release built upon it. In order to ship an SDK based on new underlying technology, we have had to defer some major features that would normally be expected to appear in an Eclipse SDK release. (See Eclipse/Eclipse SDK 4.0 FAQ for more info on the purpose/target audience of this release.)

This page summarizes the major features that we have intentionally deferred in order to ship the release, and some discussion about how these features could reappear in a future release based on the 4.x stream.

This list is not intended to be an exhaustive list of missing end-user features, but rather a guide to the "big picture" items that don't appear and why. Bugzilla remains the best way to see all the open bugs. This query can produce an open bug list.

Missing API/Developer functionality

As a plug-in developer, you will notice immediately some missing developer-level functionality. (Of course these omissions imply corresponding missing user functionality, but we focus on the developer view of them).

  • All API is provisional. Since the purpose of the 4.0 release is to get a wider community adopting the technology, we are leaving ourselves an additional release to get the API right, based on developer feedback.
  • NLS support for model files. bug 306576
  • Bidi support
  • Capabilities are not supported. bug 319865. UI will appear whether the capability is enabled or not.

Missing end user features

In some cases, end-user features that exist in 3.6 have been removed or otherwise limited in scope to allow us time to reevaluate how they should be presented in light of new e4 technology.

  • Key bindings UI. In SDK 4.0, the user must edit the workbench model description to add or change key bindings. This proves the viability of adding key bindings to a modeled workbench, but of course we don't expect this to be the way that end-users would add bindings.
  • Customize perspective. Given the increased flexibility allowed by a modeled UI, we have not put effort in the 4.0 release into modeling the same perspective functionality as in Eclipse 3.6. Future releases will bring perspectives up to par, and likely surpass the capabilities and increase the flexibility of the 3.x perspective model.

Incomplete new features

  • The e4 modeled UI architecture allows far more flexibility than before in defining the layout and composition of a UI. Things that were not possible in the Eclipse 3.x stream, such as mixing views and editors in stacks, choosing to share or not share editor areas in a perspective, or ignoring the perspective model completely, are possible now on the new architecture. We believe it's an entirely new UI design problem to incorporate this flexibility in the SDK workbench, and one that should not be undertaken lightly. Rather than expose all the flexibility of the underlying model, we have largely retained the 3.x perspective model and its limitations. We expect RCP developers to push the envelope here in the 4.0 time-frame, and will reevaluate the SDK workbench model in a future release.
  • A new search box in the 4.0 SDK gives the user access to the "quick access" feature of Eclipse 3.6. Future releases will evolve this box to a more generic search. bug 304440.

Back to the top