NewLookAndFeel

Introduction

The Eclipse 3.0 project plan has long contained an item (bug 37997, continued to bug 52685) to improve and evolve the Eclipse user experience. Here is the initial description from May, 2003:

Evolve the Eclipse user experience. Eclipse 3.0 should have a new look that makes more effective use of the capabilities of current desktop computers. This includes allowing the user to customize the workbench by creating floating toolbars and views, and supporting tear-off views and dockable toolbars where supported by the underlying window system. [Platform UI, JDT UI, SWT] [Theme: User experience]

Beginning in December, early adopters could access experimental code that implemented this new look by switching a few jar files around. Changes went far beyond the original request for floating views and dockable toolbars. Ever since the early builds, users have been providing feedback on the new look and its impact on usability through the above bugzilla entries and others (notably bug 52780 and bug 52875). In 3.0M8, the new look became the default.

What's wrong with the new look

While the progress in the addition of new features and functionality in Eclipse is laudable, some of the changes have generated a significant amount of backlash. Over 150 votes have been recorded in bugzilla for requests to roll back some or all of the user interface changes to the old look. The principal issues revolve around two main areas:

1. The new look represents a significant regression in usability in some areas compared to earlier versions such as 3.0M7, and

2. Taken as a whole, the Eclipse look and feel no longer represents a reasonable facsimile of a native application.

This has an effect not only on existing user productivity but also on the ability for the platform to draw in new users. This is most keenly, but not exclusively, felt by Rich Client developers who were originally attracted to the platform due to its clean, simple and native-appearing user interface.

Below are some key points which negatively impact usability or otherwise detract from the stated goal of achieving a native look and feel to the greatest extent possible.

(bug 58063, bug 58062, bug 58151)

The perspective switcher takes up a great deal of screen real esate in its current location in the upper right of the Workbench window. Often it will force multiple lines of the display to be used for the toolbar area due to its height or width. The perspective switcher should be a dockable control similar to a toolbar, and should be allowed on the left (as in the old look), the right, or the bottom of the window (perhaps in the status bar like fast views).

Also, the separator for perspective switcher should be native if possible. Curvy separator lines belong in games or media players, not in a serious business tool. Different platforms and themes use a multitude of fill styles for tool bars including many different types of gradient, pixmap, and/or solid fills. It is unrealistic to expect the perspective switcher widget to be able to emulate or blend well with all of these tool bar backgrounds. It would be much better for the widget to be native, and let the platform worry about aesthetic blending. As Steve Northover said at EclipseCon: "If you try to fight the operating system, you will lose."

Last Modified 10/2/06 11:59 AM

Hide Tools

Site
Changes
Index
Search

User
Log In
Register