Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [e4-dev] Declarative UI



In the Sébastien’s email, HMI means GUI. Thanks for Sébastien for the feedbacks and contributions.


I think the e4 declarative UI we should think from user perspective, instead of technology’s one. From this standpoint, we should address following developers directly and indirectly:

- Component developer

   Who is SWT aware and develop re-usable components for UI domain developers and Model designers.

- UI domain developer

   Who knows high level UI concept. He/she focuses the domain application development. They need tools to UI development like Visual editor.

- Model designer

   Who knows high level UI concept. He/she focuses the domain application development from point of view of model. They need tools to generate UI from business model.


That means we should take following issues into consideration for e4 declarative UI:

-          Easy to edit directly by human (for Component developer)

-          Direct extension support for user-defined UI elements (for Component developer)

-          Possible to integrate in Visual edition tools (for UI domain developer)

-          Support code generation via template engines (for Model designer)


Of course, there are other issues like:

-          Back compatibility and integration with existing SWT application

-          Standard

-          Technology Mature

-          Other tools




From: e4-dev-bounces@xxxxxxxxxxx [mailto:e4-dev-bounces@xxxxxxxxxxx] On Behalf Of Sébastien Moran
Sent: Thursday, December 18, 2008 3:46 PM
To: E4 Project developer mailing list
Subject: Re: [e4-dev] Declarative UI


Hi everyone,

To address one of our customers' issue I have studyied several declarative UI frameworks.
Basically, the requirements are :

  • Possibility to declaratively build SWT HMI's
  • Possibility to declaratively bind these HMI's with an EMF model
  • The framework must provide design tooling
  • The HMIs must be deployed dynamically

Another constraint is to start the developements mid-december, in other words, now :)

I have studyied Tk-UI, Wazaabi2 and XWT. These 3 frameworks come with very interesting features/concepts. In the end, XWT has been chosen. It offers pretty good tooling, declarative capabilities for both UI building and UI binding, is easy to extend in java and is the most mature.

While studying the XWT engine, I have found several things to improve, in particular the databinding with an EMF model.

For the moment we plan to use it and improve some parts. These modifications could be contributed in the future.



Kevin McGuire a écrit :

Hi folks,

Remy has reminded me that there's been no recent discussion on declarative UI.  I know there was an intention for people to get together at ESE and discuss the topic.  I guess I was hoping for some kind of output from that.

I've been pretty heads down on getting the CSS code working so ... it'd be good if those who were at ESE and who care about declarative UI could get the ball rolling again.




e4-dev mailing list

Back to the top