Skip to main content
Jump to: navigation, search

Difference between revisions of "Eclipse4/KnownIssues/4.0"

Line 1: Line 1:
The Eclipse SDK 4.0 Early Adopter release is not intended to replace the Eclipse 3.6 SDK.  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 entirely new underlying architectures, we have had to defer some major features that would normally be expected to appear in an Eclipse SDK release.  (See the Eclipse SDK 4.0 Early Adopter FAQ for more details about the release).
+
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 entirely new underlying architectures, we have had to defer some major features that would normally be expected to appear in an Eclipse SDK release.  (See the Eclipse SDK 4.0 Early Adopter FAQ for more details about the 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.
 
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.

Revision as of 10:13, 15 July 2010

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 entirely new underlying architectures, we have had to defer some major features that would normally be expected to appear in an Eclipse SDK release. (See the Eclipse SDK 4.0 Early Adopter FAQ for more details about the 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.

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
  • Bidi support
  • Capabilities are not supported. bug 304440. 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 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 (for things like mixing views and editors, not sharing editor areas, ignoring perspectives completely), we have not put effort in the 4.0 release into modelling the same 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

  • 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