Eclipse XWT 0.10.0

Release Date
Deliverables
  1. XWT Parser
  2. SWT integration
  3. JFace Integration
  4. JFace DataBinding support
  5. EMF Databinding support
Compatibility

The XML markup is compatible with the previous releases published in e4. But the root package of all classes is renamed from "org.eclipse.e4.xwt" to "org.eclipse.xwt".Therefore the applications that use directly Java APIs need to be migrated to this release.  

Internationalization

The plugin supports the i18n to build the UI with any languages.

Target Environments

Java

1.5 +

OS

Windows 7 32 & 64 bits

Mac OS 10.5.0 +

Linux

Eclipse

Kepler and Luna

 

Name Date Description
M1 2013/11/27 This is the first public build as a standalone project after the migration from e4. It integrates the fixe on "Custom URL protocols are not supported" https://bugs.eclipse.org/bugs/show_bug.cgi?id=404413
RC 2013/12/11 This build includes the bug fixes found in M1. This release is in fact the release candidate. 1. Add the missing plugin org.eclipse.xwt.emf to support EMF data binding https://bugs.eclipse.org/bugs/show_bug.cgi?id=423379 2. Add a new features to support the nested properties in binding path https://bugs.eclipse.org/bugs/show_bug.cgi?id=423749
Release 2013/12/19 The final release.
Themes

Full feature releases

All features developed in e4 are available. And some Snippets are also provided.
  • Make "trident" dependency optional [301354] (target milestone: 0.10.0 M1)
  • XWT locks on initialization with GTK [347742] (target milestone: 0.10.0 RC)
  • Provide a test case that uses the EMF data binding support [423862] (target milestone: 0.10.0 RC)
  • remove org.eclipse.ui dependencies [397502] (target milestone: 0.10.0 M1)
  • Branding aka 'About dialog' [399818] (target milestone: 0.10.0 M1)
  • Custom URL protocols are not supported [404413] (target milestone: 0.10.0 M1)
  • EMF plugin is missing. [423379] (target milestone: 0.10.0 RC)
  • Make bindingPath support nested properties [423749] (target milestone: 0.10.0 RC)