Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search


< Eclipse‎ | Incubator
Revision as of 12:42, 20 November 2008 by (Talk | contribs) (Interested Parties)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)



UFacekit is a proposed open source component under the Eclipse Incubator project. UFacekit's purpose is to:

  • improve adoption of Eclipse Core technologies (like Eclipse-Databinding) outside RCP and SWT (e.g. Swing, GWT, QT)
  • improve usability of Eclipse-Databinding by providing a high-level Widget-API

This proposal is in the Project Proposal Phase and and is written to declare its intent and scope. This proposal is written to solicit additional participation and input from the Eclipse community. You are invited to comment on and/or join the effort.


Since the 3.3 release, Eclipse ships an actively developed and extended databinding framework (Eclipse Data Binding) that eases the development of UI applications backed by a model. At the time of the 3.4 release of Eclipse, the Eclipse Data Binding framework had been adopted by many RCP applications and new libraries supporting model implementations (EMF) besides JavaBeans(tm). So far, we have not seen support for other widget toolkits (such as for example Swing, GWT, etc.) although the main framework is designed to make this possible. This means that the Eclipse Data Binding framework cannot currently be used in applications which are not using SWT and JFace, although there is no good reason not to do so.

UFacekit was started a year ago by James Strachan and Tom Schindl (Angelo Zerr and Kenneth Westelinck joined the project later) with the following set of targets:

  • Promote reuse of rich UI code across Eclipse (JFace/SWT), GWT and Swing runtimes by providing a facade around different UI-Technologies.
  • Promote the use of Eclipse Data Binding within GWT and Swing communities by providing Eclipse Data Binding Observable implementations for them.
  • Make new applications stacks accessible to EMF (e.g. Swing).
  • Simplify rich UI development by providing simpler facades and powerful binding.


UFacekits scope is to develop highlevel API and framework modules to develop applications in a widget-toolkit independent fashion which are small and easy to extend (e.g. create an implementation for other widget-toolkits, use different widget types, Nebula-Grid instead of SWT-Table). UFacekit differs in this scope with SWT as it won't provide access to lowlevel drawing operations like GC but only provides the minimal needed subset of methods needed to develop applications which makes the task of extending and porting to new technologies easier.

Besides the widget-toolkit neutral API UFacekit will provide established eclipse technologies/modules for currently not support platforms/runtimes (EMF for GWT, Databinding for GWT) and implementation of Databinding-Observables and JFace-Viewer implementations for currently not support model-technologies and widget-toolkits.

UFacekit Design

UFacekit is designed in a modular way as OSGi-Bundles to use its subcomponents with a minimal set of dependencies. For example, if a developer only wants to use Eclipse-Databinding in his/her project she will only use the Swing-Observables-Bundle, if he/she only wants to use a light weight model implementation he/she only takes the UBean-Bundles.

As already mentionned all UFacekit deliverables are packaged as OSGi-Bundles. By following the OSGi-standards it can be used with any OSGi implementation following the standards (Felix, Knopplerfish, ...).


The above design keeps the UI code free from the toolkit Code and holds as few information as possible about the modeling technology (maybe this could be removed completely in the future).

An UBean-Example:

public void createUI(UIComposite root, UBeanForm form, IObservableValue value) {
  UIFactory ui = root.getFactory();
  // The UI setup
  InputFieldUIInfo uiInfo = = new InputFieldUIInfo(GridLayoutData.fillHorizontalData(),InputFieldUIInfo.SIMPLE);
  UIInputField idField = ui.newInputField(detailComposite, uiInfo);
  // The Binding setup
  InputFieldBindingInfo bindingInfo = InputFieldBindingInfo.newTextFieldInfo(form.detailValue(Person.ID, int.class));
  form.add(idField, bindingInfo);
  // Bind the master value

An EMF-Example:

public void createUI(UIComposite root, EMFForm form, IObservableValue value) {
  UIFactory ui = root.getFactory();
  // The UI setup
  InputFieldUIInfo uiInfo = = new InputFieldUIInfo(GridLayoutData.fillHorizontalData(),InputFieldUIInfo.SIMPLE);
  UIInputField idField = ui.newInputField(detailComposite, uiInfo);
  // The Binding setup
  InputFieldBindingInfo bindingInfo = InputFieldBindingInfo.newTextFieldInfo(form.detailValue(PersonPackage.Literals.PERSON__ID, int.class));
  form.add(idField, bindingInfo);
  // Bind the master value


The following screenshots are based on the exact same code base, the only difference being the initial composite (the Shell used as a root).





MyGWT (ancient and has to be rewritten)


Relationship with other Eclipse-based Projects

UFacekit has a strong relation to the following projects:

  • Eclipse-Databinding (Core & JFace) providing the foundation for the high-level API
  • EMF (As a Databinding possibility, GWT support for EMF-Models)
  • E4 (SWT-Port for the web, create a class-lib for missing GWT-classes (e.g. Runnable) )
  • Riena where some of the targets overlap (e.g. highlevel Databinding API)


Initial Committers

  • Tom Schindl - BestSolution Systemhaus Gmbh - (component lead)

    Tom is self-employed and CEO of Systemhaus Gmbh a software company building applications (RCP, J2EE) for companies around the world. Besides implementing solutions their own consulted companies to introduce Eclipse Technologies into their software stack by providing its knowledge about Eclipse Technologies and Software Design experience.

    Tom is one of the Platform-UI and Nebula committers working on JFace-Viewers, Nebula-Grid and contributed patches to other eclipse projects (EMF, ...). He is part of the E4 project team and wrote the EMF based platform prototype used as the starting point for the implementation of the next generation of the Eclipse-Platform.

    He is a regular contributor to the eclipse newsgroups and received the top contributor award in 2007 for his work on JFace-Viewers.

  • James Strachan - Progress Software -

    James works in the FUSE group at Progress and is a long time contributor to open source projects mostly at Apache and works on projects like ActiveMQ, Camel and ServiceMix

  • Angelo Zerr - Independent -

    Angelo is the developer of TK-UI, a toolkit to manage CSS Styling/Declarative UI (XUL, XHTML) which renders to Swing and SWT. He has also developed Akrogen, an Eclipse plugin for code generation where you can describe Eclipse Wizard with XUL and Javascript and link it with template (Freemarker, Velocity, XSL...) or Ant Task to generate code.

  • Kenneth Westelinck - Ebit NV -

    Kenneth is a senior Java Software Engineer at Ebit NV specialized in building custom J2EE, Hibernate and Spring based applications for disparate types of clients. In the past, his main focus has been solving application integration problems for clients, using both Commercial and Open Source software (Mule). Kenneth is a regular contributor to the Mule ESB platform and active on the mailing lists. Currently he's working on technical projects for an engineering company involving Eclipse RCP GUIs for monitoring and administration purposes.

Initial Code Contribution

EPL licensed code coming from UFacekit-Project.

UFacekit dependes on some external opensource modules:

  • GWT (Apache License V2.0 already IP approved)
  • GWT-logging (Apache License V2.0, See Homepage)
  • Rhino (MPL, Consumed from Orbit)
  • Log4j (Apache License V2.0, Consumed from Orbit)
  • SwingX (LGPL)

Interested Parties

Anyware Technologies

OnPositive Technologies

Tentative Plan

Initial objectives

  • a highlevel, widget-toolkit and model-indepent Widget API to easily bind widgets (including validation and decoration support)
    • UI
      • implementation for SWT/JFace
      • implementation for Swing
    • Model
      • JavaBeans
      • EObjects (EMF)
      • UBeans
  • Observable implementations for Swing
    • JFace-Viewers for Structured-Swing-Controls (List, Table, Tree)
  • Observable implementations for UBean
  • Observable implementations for XML-DOM
  • org.eclipse.core.databinding for use in GWT applications based upon current stable Eclipse release
  • Observable implementations for GWT-Widgets

Additional objectives considered for later

  • GWT support for EMF-Core-Modules
  • Support for Eclipse-Forms
  • Support to define UI and UFacekit-Applications (Upplication) using EMF
  • Support to design Upplications using GEF
  • Support for other Java-UI-Toolkits (QT-Jambi, DOJO, ...)
  • Declarative Styling (EMF-Model/CSS)

Milestone Plan

Q4 - 2008: Milestone 1 (all objectives implemented (SWT & Swing))

Q1 - 2009: Milestone 2 (all objectives for an initial version implemented)

Back to the top