Standalone SWT download is now an Eclipse project |
For developers of standalone SWT applications, the SWT component is available as a separate download. For Eclipse 3.1, the SWT download can now be easily imported into your workspace as a project.
The org.eclipse.swt project you have imported defines the location of the native libraries so you can run your application with the standard Java or JUnit launchers. |
Starting SWT standalone applications using PDE |
To run and debug your SWT application using the SWT plug-in from Eclipse, you can use the new SWT application launcher to locate the native libraries. A shortcut to the launcher is available in the context menu of your Java class via Run As > SWT Application. |
Advanced graphics |
New API has been added for advanced graphics operations such as path for curves and lines, alpha blending and transformations. This new API requires the Cairo Vector engine on GTK and Motif, and GDI+ on Windows. For more details see the example snippet. |
New Link widget |
The new For more details, see the example snippet. |
Strike through and underline in StyledText |
Text can be underlined or
a strike can be drawn through it with the new For more details see the example snippet. |
CVS outgoing change sets |
Outgoing change sets allow you to organize outgoing changes into logical groups before they are committed. To enable outgoing change sets, put the Synchronize view into Outgoing mode, click on the change set button in the Synchronize View, then select an outgoing change and choose Add To > New Change Set... from the context menu. You can also appoint a change set as the default and have all subsequent outgoing changes added to that set automatically. Commands on the context menu allow outgoing changes to be moved between change sets. When the change set is committed to the CVS repository, the comment associated with the change set is used as the CVS commit comment. |
Support for
CVSNT |
Thanks to the efforts of the CVSNT developers, the Eclipse CVS client now supports CVSNT. CVSNT versions greater than 2.0.58b have been tested with Eclipse 3.1. |
CVS commit review |
The commit dialog now includes a list of the
files that are being committed. This makes it easy to browse the files
while writing the commit comment, and to hold back certain files by removing
them from the list. It's especially useful when committing directly from
the Package Explorer or Navigator view.
There are also CVS preferences (Team > CVS) for determining whether commit comments are mandatory and for specifying the maximum number of files that should be displayed when committing. |
CVS improved file type support |
CVS now prompts whenever a file with an unknown file type is about to be committed. This allows you to explicitly configure a file type instead of CVS picking binary as the default. Also, file type decisions can now be based on the file name alone (e.g. Makefile), not just the file extension. |
CVS branch and merge |
The CVS branch wizard now lets you use content
assist to pick a branch from a project already branched in your workspace.
When merging you can simply specify the end tag and the wizard will automatically find the appropriate start tag. If a start tag is not available, you can still merge without seeing a preview in the Synchronize view. |
Ant debugger |
The new Ant debugger helps you debug the execution
of your Ant buildfiles. It includes the standard debugger features like
breakpoints, stepping, dependency call stack, and run-to-line support.
The presentation of Ant properties are also grouped in the Variables view
for your convenience:
|
Ant editor improvements |
Several improvements have been made to the
Ant Editor, including:
|
Ant target per build kind |
The Targets tab for an Ant builder allows you to specify the target(s) that should be executed for each build kind. This includes the target to execute when you invoke a "Clean". |
New features for the Console |
Significant improvements have been made to the Console view
|