Sapphire aims to raise UI writing to a higher level of abstraction. The core premise is that the basic building block of UI should not be a widget (text box, label, button, etc.), but rather a property editor. Unlike a widget, a property editor analyzes metadata associated with a given property, renders the appropriate widgets to edit that property and wires up data binding. Data is synchronized, validation is passed from the model to the UI, content assistance is made available, etc.
Release themes, priorities and features are listed in the plan document.
There is no declared API in this release as both the API and the API policy are still evolving. Separation between API and internal code does exist. Documentation is improving.
The following chart summarizes bugs targetted to this release as of the last update of this document. Click through to see an updated view.
Talk at EclipseCon 2011. All discussion happens on open channels of developer mailing list, adopter forum and bugzilla.
Multiple active adopters visible on project's communication channels. Three of these adopters have contributed patches so far. At least one adopter (besides Oracle) has shipped software with features built using Sapphire.
Java EE Configuration Editors Project created under Web Tools Project to (in part) serve as a prominent and open source example of a complex feature built using Sapphire.
The project leadership verifies that the Eclipse IP policies and procedures have been followed
Back to the top