Albireo Release Notes

To get the latest Albireo release, go to the Albireo download site. To install Albireo, see the Albireo Installation page.

Version 0.0.2 (alpha 2) 5/23/08

Changes:

• SWT.BORDER SwingControls now participate properly in focus management
• A StackOverflowError when embedding Swing in the Eclipse IDE has been eliminated
• SwingControls no longer accept focus when embedded Swing components are not focusable.
• Initial caret position in embedded Swing text controls is now set correctly
• Optional improvements to participation of Swing controls in SWT tab cycles (see SwingControl.setSwtTabOrderExtended()).
• A bug has been fixed where initial rendering of the embedded Swing component was sometimes skipped.
• Focus is now properly set on Swing components even if the request is made to the parent SWT composite before they are created on the AWT Event thread.
• AWT modal dialogs are no longer displayed on top of windows from other applications.
• On GTK, AWT modal dialogs are no longer intermittently hidden behind SWT shells from the same application.
• A bug where SwingControls would occasionally steal focus from other windows has been fixed.

Alpha 1 4/16/08

Prerequisites: Eclipse 3.3 or higher (probably 3.2 is enough as well); JRE 1.4 or higher, but our testing has focused on JRE 1.5 and 1.6, so either of those versions is highly recommended.

Initial Features

Synchronized Look and Feel. Where possible the Swing look and feel is changed to the native platform look and feel, so that the appearance of Swing components is consistent with SWT widgets. Fonts and colors are propagated from SWT when creating Swing components.

Resize flicker. Flicker while resizing Swing components is greatly reduced under Windows. This particular problem is not yet solved on other platforms.

Modal dialogs. SWT input is blocked while AWT modal dialogs are displayed.

Focus management. Tab traversal between Swing and SWT components is supported. Swing focus is maintained when clicking on a parent RCP view tab. Swing components can be activated with a single click. (In some cases, two clicks are needed when using the SWT_AWT bridge alone). On GTK, some problems remain with focus being stolen by Swing components when they are originally created.

Keystroke Contention. A conflict between Swing and the native windowing system when typing Shift-F10 is resolved.

Size/Layout Management. The preferred sizes of Swing components are respected in SWT layouts. Changes to the size of the containing SWT composite are propagated to the embedded Swing component. There are some remaining problems with usage of the SWT.BORDER style.

Popup Menus. SWT popup menus can be assigned to most Swing components through an API. Swing popup menus are properly dismissed when a SWT menu is opened. (This works with one exception: opening the system menu in the upper left hand corner of the window does not dismiss an open Swing dialog)