The Eclipse release cycle begins anew. To kick things off after the successful first Callisto simultaneous release, here are some of the more noteworthy things available in milestone build 3.3M1 (August 10, 2006) which is now available for download. See the build notes for details about bugs fixed and other changes.
SWT |
|
| Printing support added on GTK+ | Printing support has been added to SWT for GTK+. It is important to note that you must be running with GTK+ 2.10 or newer in order for this support to be utilized. |
| |
|
| Option to print line numbers added to StyledText | When printing a StyledText widget, line numbers
can now be printed by setting the StyledTextPrintOptions.printLineNumbers
field to true. |
| |
|
| System tray support added on Mac OS X | Icons placed on the system tray will now appear
in the Mac OS X status bar.
|
| |
|
| Writing PNGs now supported | Images can now be written to disk in PNG format (example snippet). |
| |
|
| Browser profiles now utilized on GTK+ and linux-motif | The Browser widget is now utilizing profiles on GTK+ and linux-motif. As a result many previous shortcomings have been fixed, including the inability to display https pages, not rendering visited links properly, and not caching visited pages. |
| |
|
| Browser support added on PowerPC | Browser support has been added for the PowerPC architecture (GTK+). |
| |
|
| GtkComboBox now utilized when available | GtkComboBox is now utilized natively for users
that are running with GTK+ version 2.4 or newer.
|
User Assistance |
|
| Help home button | The help window now has a Home
button in the navigation toolbar, which brings you back to the initial product-configurable
home page.
|
| |
|
| Help search term highlighting | If you open a help document as a result of a
search, a new toggle button will appear in the toolbar allowing you to toggle
the search term highlighting on and off, making the document easier to read.
|
Debug |
|
| Browse all references (J2SE 6 only) | If you're running your Java application with
a J2SE 6 virtual machine, you can browse all references to an object in
the variables view. Select any object in the variables view, and choose
All References from the context menu. A pop-up displays
all objects referring to the selected object. You can expand each node in
the tree to follow references to each object. You can inspect any object
in the reference tree by selecting it and pressing Ctrl+Shift+I.
This opens an inspect pop-up displaying the object's fields.
|
| |
|
| No more prompting | A user preference now controls whether you are
prompted to confirm the deletion of all breakpoints in the workspace. The
new preference is available on the Run/Debug preference
page. As well, a check box in the confirmation dialog allows you to set
the preference.
|
| |
|
| Auto format stack traces | Stack traces can be formatted automatically as
you paste them into the Java stack trace console. An "Auto
Format" toggle is available on the console tool bar.
|
| |
|
| Double-click and Ctrl+Shift+B for all kinds of breakpoints | Double-clicking in the vertical ruler, or invoking
Toggle Breakpoint (Ctrl+Shift+B), now creates an appropriate
kind of breakpoint based on the cursor location - line breakpoint, watchpoint,
method breakpoint, or class load breakpoint. To create a class load breakpoint,
double click on the class declaration line.
|
Platform Text |
|
| Scroll by pages using Ctrl + mouse wheel | The mouse wheel scrolls the content of a textual editor by pages while the Ctrl key is pressed. |
| |
|
| More flexible templates | The syntax for templates has evolved to allow
typed and parameterized template variables. This allows the same variable
type to be used multiple times in the same template. As an example, consider
the following template for generating a doubly nested for loop:
|
| |
|
| Contribute columns to vertical ruler | A new extension point, org.eclipse.ui.workbench.texteditor.rulerColumns
allows the contribution of columns to the vertical ruler of any text editor.
|
JDT UI |
|
| Scripted refactorings | Now all refactorings offered by the Java Development
Tools can be scripted, including Move, Copy, Paste, and Delete.
Use Refactoring > Create Script to create a script from the refactoring history and Refactoring > Apply to apply one.
|
| |
|
| More Java search options | The Java search dialog has been extended to offer
finer control to limit the scope to search in sources, JRE libraries, required
projects, and application libraries.
|
| |
|
| Paste type declaration creates new project | Ever wanted to quickly try out a code snippet
somebody sent to you? Copy the snippet to the clipboard, go to the Package
Explorer, select nothing, and choose Edit > Paste (Ctrl+V).
Eclipse will try to parse the contents of the clipboard, and if it looks like contents for a *.java file, it will create a new Java project and paste the *.java file.
Like in 3.2, you can, of course, still select an existing project or package as target for the new file. |
JDT Text |
|
| Template for adding JUnit 4 test methods | A new Test template has been added to speed up adding JUnit 4 test methods. |
| |
|
| Configurable Javadoc font | The font for displaying Javadoc is now configurable
on the General > Appearance > Colors and Fonts preference page.
The Javadoc display font is used by the Javadoc view and hover, and
for the additional information shown during content assist.
|
| |
|
| Syntax coloring for brackets | Brackets may now be colored separately from operators
in the Java editor via the Java > Editor > Syntax Coloring
preference page.
|
Update/Install |
|
| |
|
| Install wizard improvements | The Installation page of the Install wizard now
presents features in an easy-to-use table that includes the name, version,
size, and target location of each feature. A Change Location button lets
you easily change the target location of the selected features.
|
Team/CVS |
|
| Import CVS projects directly into working sets | You can now assign CVS projects to a working
set during the import step. This is available from both the CVS Repository
View (via Check Out As) and through the CVS Import Wizard.
|
| Export working sets as part of
team project set |
The export wizard is now able to persist active
working sets as part of a Team Project set.
|
| History view search |
The History View has a new search field which
allows you to perform a quick search on the displayed revisions. The search
compares the author, comment, revision, and tags against the entered string.
The field is accessible via the drop down menu.
|
PDE |
|
| Content assist in plugin.xml | Content assist (Ctrl+Space)
is now available on the plugin.xml source page to give you context-sensitive
information as you create extensions and extension points. Features include:
Note that the content assist can be activated without the need for a partial string. PDE uses extension point schemas to determine which elements and attributes are suitable for the current context.
|
| Content assist in MANIFEST.MF | Content assist (Ctrl+Space)
is now available on the MANIFEST.MF source page, including completion proposals
for:
|
| Field assist in Forms | All fields denoting classes in the plug-in manifest
editor now support a field assist feature to help you complete the name
of a partially entered class name.
This feature works in a similar way to the content assist in the Java editor, and supports package names and CamelCase.
|
| Hyperlinking and open declarations | Hyperlinking (i.e. the use of Ctrl+Left
to navigate from one editor to another) is now supported on the plug-in
manifest editor source page. The usage of the F3 key to
open declarations is also supported and provides the same functionality
as hyperlinking.
Hovering over attribute values on the plugin.xml page and pressing Ctrl+Left can be used to
Hyperlinking provides additional functionality on the MANIFEST.MF source page including:
|
| Code folding | Folding is now supported on the plugin.xml and
MANIFEST.MF source pages of the plug-in manifest editor to make large files
more manageable.
The option to turn folding on and off can be found on the Plug-in Development > Editors preference page.
|
| Code formatting | Line wrapping introduced by some packaging tools
make the plug-in MANIFEST.MF file hard to read. PDE now provides a Format
action in the context menu of the MANIFEST.MF source page to format the
contents of the file into something more human-readable.
|
| |
|
| Filtered extensions | The Extensions tab of the plug-in
manifest editor allows the filtering of the Extensions tree based on a text
filter. This function is particularly useful when searching for that one
contribution among a long list of extensions.
|
| |
|