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.
Difference between revisions of "FAQ What is new in Eclipse 3.0?"
| Line 66: | Line 66: | ||
The Eclipse 3.0 plan (http://eclipse.org/development/plan) | The Eclipse 3.0 plan (http://eclipse.org/development/plan) | ||
| + | |||
| + | <hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font> | ||
Revision as of 16:09, 14 March 2006
Attempting to enumerate all of new features and APIs in Eclipse 3.0 would be futile. The past year or so of development has focused on more than 50 major features of the Eclipse 3.0 plan, not to mention addressing more than 5,000 bugs and feature requests, according to a quick query of the Eclipse Bugzilla. The best place to get an overview of major new changes in Eclipse 3.0 is to read through all the New and Noteworthy documents included with each milestone build.
To give you a quick summary, the development of Eclipse 3.0 has centered
on the following major themes:
- User experience. This theme deals with all aspects of the end user
experience, especially for new users, the so-called out-of-box experience. This theme also focuses on UI scalability, affordances, improved file-encoding support, key bindings, editor management, text editor presentation, workspace selection, and the introduction of an SWT browser widget.</li>
- Responsive UI. This involves identifying and reducing the number of places where
users are forced to wait when using Eclipse. Major work on this theme included the introduction of an Eclipse concurrency architecture and tackling the performance gap in Eclipse between Windows and other platforms, such as Linux GTK, QNX, and Mac. </li>
- Rich client platform. The Eclipse APIs have been
reorganized to better support development of applications outside the development tools domain. Work on this theme also included a new infrastructure for storing user settings and support for dynamic installation and removal of plug-ins.</li>
- Extended Java family. This theme deals only with the Java development tools
subproject. Work in this area focused on opening up the JDT APIs to better support Java-like source files, such as Java Server Pages (JSPs) and SQLj. This included opening up the refactoring and Java search infrastructure to facilitate participation by third-party plug-ins.</li>
See Also:
FAQ_Is_Eclipse_3.0_going_to_break_all_of_my_old_plug-ins?
The Eclipse 3.0 plan (http://eclipse.org/development/plan)
This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.