Jump to: navigation, search

Difference between revisions of "Eclipse4/KnownIssues/4.1"

(Eclipse 4.1 SDK)
Line 2: Line 2:
  
 
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>
 
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>
 +
 +
This page is intended to let you know what issues have already been identified. This is a living document and will be updated at the end of each milestone. It represents the current state of the 4.1 SDK's compatibility layer for those that decide to switch over to the new world.
  
 
== Known Issues  ==
 
== Known Issues  ==
Line 7: Line 9:
 
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).
 
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.  
+
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.<br>
  
Known Issues:
+
=== 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
 +
*There may be instances where an item is visible or enabled when it should not be
 +
*
  
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.
+
<br>
  
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 ==
+
== 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:
+
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
+
- Detached Windows can contain multiple stacks - You can mix editors and views in the same stack  
 
<div><br></div>
 
<div><br></div>

Revision as of 15:22, 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.

This page is intended to let you know what issues have already been identified. This is a living document and will be updated at the end of each milestone. It represents the current state of the 4.1 SDK's compatibility layer for those that decide to switch over to the new world.

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.

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