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:
 +
= Eclipse 4.1 SDK  =
  
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.
+
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.In general we've achieved this, 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.<br>
  
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.
+
== Known Issues  ==
  
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.
+
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. We expect many of these issues to be addressed before 4.1 ships with the remainder to be addressed during the 4.2 development cycle (see below).
  
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:
+
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.
 
+
- Detached Windows can contain multiple stacks
+
- You can mix editors and views in the same stack
+
  
 
Known Issues:
 
Known Issues:
Line 15: Line 13:
 
No Intro:  
 
No Intro:  
  
The Welcome screen will not appear for fresh workspaces.
+
The Welcome screen will not appear for fresh workspaces.  
  
 
Menu/TB Issues:  
 
Menu/TB Issues:  
  
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:
+
CSS / Style Issues:  
  
The UI is not yet completely polished, so there may be some rendering artifacts (especially after changing Themes.
+
The UI is not yet completely polished, so there may be some rendering artifacts (especially after changing Themes.  
  
No Fast Views:
+
No Fast Views:  
  
This was intentionally dropped since it has been subsumed by the ability to minimize any stack to the trim.
+
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.
 
Cannot dock the Perspective Switcher on the left.
 +
 +
== Known Advantages ==
 +
 +
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
 +
<div><br></div>

Revision as of 12:15, 10 March 2011

Eclipse 4.1 SDK

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.In general we've achieved this, 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.

Known Issues

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. We expect many of these issues to be addressed before 4.1 ships with the remainder to be addressed during the 4.2 development cycle (see below).

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.

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.

Known Advantages

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


Back to the top