Eclipse 3.1M6 发布了...

2008-02-23 10:00:23来源：互联网阅读 ()

Here are some of the more noteworthy things available in milestone build M6 (April 1, 2005) which is now available for download. See the M6 build notes for details about bugs fixed and other changes.

Platform UI

Curry tracking

The Eclipse teams in Ottawa are now tracking the number of takeout dinners ordered from Shaan Curry House during the 3.1 release cycle.

Please keep in mind this only represents a small portion of our curry orders - we're in the process of entering data back to September 2004; the full database will be found here.

Performance view

There is now a view for displaying performance issues in Eclipse. Several operations throughout Eclipse now report performance to the org.eclipse.core.runtime.PerformanceStats class when time to perform an operation is over a threshold. Performance logging occurs if you run Eclipse with the -debug option.

These performance issues are logged to an internal performance.log file (in the .metadata directory of your Eclipse workspace) for further analysis. See here for more details.

Preference page links

General support for linking preference pages allows pages with related settings to refer to each other and provide quick Access to the other page. Combined with Web-style forward and backward navigation added in an earlier milestone, it is now much easier to work with a set of related preference pages.

Content type preference page

A new preference page to edit content types and their associated file names and character sets has been added under the General/Editors preference page.

Editor lookup based on content type

Editor lookup now takes content types into account via a new element in the org.eclipse.ui.editors extension point called contentTypeBinding. Editors may now advertise that they are capable of working on certain content types as well as their traditional file name and extensions. For M6, content type bindings take precedence over file name bindings, but we will be looking at more sophisticated policies for M7. Note that the various SDK editors, including the Text, Java, and Class file editors, will not take advantage of this new feature until M7.

New capabilities preference page

A new capabilities preference page has been introduced in an effort to simplify management of capabilities in downstream products.

Dynamic Help now available for all the dialogs

The new dynamic help that was added to the workbench window in M5 is now available in dialogs as well. When triggered by the system-specific help shortcut (F1 on Windows, Shift-F1 on Linux GTK etc.), a shell opens aligned with the dialog showing the related help information. Multi-page dialogs like wizards, preferences, launch configurations, searches, etc. trigger the help pane to update its content as you flip from page to page.

Workbench Browser support API now available

Starting from M6, the web browser support API is available to clients from IWorkbench. The API makes it straightforward to programmatically open URLs from plug-ins. URLs are opened in internal or external browsers, depending on user preferences. Browser support is pluggable and Eclipse provides an RCP-friendly reference implementation in the new org.eclipse.ui.browser plug-in.

In addition, the internal web browser is reGIStered as a non-default editor for the most common HTML extensions.

Platform Runtime

Single JAR plug-ins

Eclipse now provides the ability to ship a plug-in packaged as a single JAR file rather than as a directory of files. Think of this as folding the plug-in metadata (plugin.XML etc.) into its code JAR. This move has a number of benefits ranging from smaller footprint to easier/faster install to fitting better with the standard Java notion of JARs. More information can be found on the Core team web page.

In Eclipse 3.1 M6 all of the RCP base plug-ins and a few extra (over 25 in total) are shipped as JARs in all distributions (RCP, Platform, PDE, JDT , etc drops). For M7 we expect the vast majority of Eclipse plug-ins to be JAR'd.

JAR'd plug-ins are the new best practice for Eclipse packaging.