You are browsing past revisions for this area.

Date Editor Preview
You are previewing another version of this material. This will not become the current version unless you click "Revert." If you change your mind, click "cancel."

The next generation UI

Wazaabi provides a complete a complete model support for describing UI in SWT, SWING and JSF, but can be extended to other UI technologies.


Engine: The true controller

The Engines

The engines are responsible for rendering the model to the target UI technology. This section describes how the engine are linked to the model and the UI. In order to highlight the Engine behaviour we will take the SWT example with a special focus on the Text widget, from the model to the SWT Text widget.

Project Architecture

The Engines projects are segmented exactly as the models are, the project org.wazaabi.engine.core contains the common engine behaviour for all target UIs, while org.wazaabi.engine.SWT contains the real implementation of the edit parts for the SWT target.

  • Model-engine

The Wazaabi EditPart, the true controller

The Wazaabi Engines are composed by Edit part realizing the link between the model UI and the final target UI widget. The Wazaabi edit part extends the real org.eclipse.gef.editparts.AbstractEdit part for which the aim is really to be the controller between the UI model and the final figure which is in our case, the real UI widget. Let's take the SWT implementation example for the rest of the section.