Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Eclipse4/KnownIssues/4.1"

Line 1: Line 1:
The Eclipse 4.1 SDK is already substantially ready. We on the Platform team have been using it for months and are generally satisfied with its usability, performance and robustness, and the overall rate of convergence. By the time 4.1 ships, we expect that the Eclipse community at large should be able to use it for development without impacting their productivity and would even expect that most plug-ins will run correctly on top of it.
 
  
The focus on 4.1 has been on bringing it up to a point where it's functionally usable on a day-to-day basis. we've achieved this at least to the point where we feel confident enough to garner input from a wider audience in the eclipse community. There are however parts of the existing eclipse
+
The focus on 4.1 has been on bringing it up to a point where it's functionally usable on a day-to-day basis. we've achieved this at least to the point where we feel confident enough to garner input from a wider audience in the eclipse community. We have a ways to go before we can match the legacy eclipse's 100+ <i>Million</i> man-hours of use but it's time to begin putting more eyes and hands on it.
  
:
+
There are however parts of the 4.1 SDK where we have already identified issues that new users are sure to notice. Note that we've tried to allocate our time specifically on those areas that directly affect the usability of the SDK.
  
API Completeness: Ensuring that we have the ability to seamlessly run at least the majority of plug-ins.
+
Please report <i>any</i> loss of functionality as a defect. One of the advantages of working on the E4 codebase is that our bug 'fix' rate is far above that of the 3.x stream, meaning that the time between a defect being reported and a fix arriving is many times a matter of hours, not days.
Robustness: Making sure that you can work with 4.1 in the same manner that you do currently with the 3.x stream.
+
  
There are a number of known issues that you will immediately notice when using Eclipse 4.1:
+
On the plus side there are a number of things that you can do in the 4.1 SDK that you cannot do in 3.x:
  
No Intro: While serious for enterprise products this will generally not affect the functionality of the system
+
- Detached Windows can contain multiple stacks
 +
- You can mix editors and views in the same stack
 +
 
 +
Known Issues:
 +
 
 +
No Intro:  
 +
 
 +
The Welcome screen will not appear for fresh workspaces.
  
 
Menu/TB Issues:  
 
Menu/TB Issues:  
Line 16: Line 21:
 
We are still experiencing ordering issues with menu and toolbar items.
 
We are still experiencing ordering issues with menu and toolbar items.
 
There may be instances where an item is visible or enabled when it should not be.
 
There may be instances where an item is visible or enabled when it should not be.
 +
 +
CSS / Style Issues:
 +
 +
The UI is not yet completely polished, so there may be some rendering artifacts  (especially after changing Themes.
 +
 +
No Fast Views:
 +
 +
This was intentionally dropped since it has been subsumed by the ability to minimize any stack to the trim.
 +
 +
Cannot dock the Perspective Switcher on the left.

Revision as of 17:53, 9 March 2011

The focus on 4.1 has been on bringing it up to a point where it's functionally usable on a day-to-day basis. we've achieved this at least to the point where we feel confident enough to garner input from a wider audience in the eclipse community. We have a ways to go before we can match the legacy eclipse's 100+ Million man-hours of use but it's time to begin putting more eyes and hands on it.

There are however parts of the 4.1 SDK where we have already identified issues that new users are sure to notice. Note that we've tried to allocate our time specifically on those areas that directly affect the usability of the SDK.

Please report any loss of functionality as a defect. One of the advantages of working on the E4 codebase is that our bug 'fix' rate is far above that of the 3.x stream, meaning that the time between a defect being reported and a fix arriving is many times a matter of hours, not days.

On the plus side there are a number of things that you can do in the 4.1 SDK that you cannot do in 3.x:

- Detached Windows can contain multiple stacks - You can mix editors and views in the same stack

Known Issues:

No Intro:

The Welcome screen will not appear for fresh workspaces.

Menu/TB Issues:

We are still experiencing ordering issues with menu and toolbar items. There may be instances where an item is visible or enabled when it should not be.

CSS / Style Issues:

The UI is not yet completely polished, so there may be some rendering artifacts (especially after changing Themes.

No Fast Views:

This was intentionally dropped since it has been subsumed by the ability to minimize any stack to the trim.

Cannot dock the Perspective Switcher on the left.

Back to the top