Hi Dave,

 

XWT uses an object dynamic mapping concept, which can connect to any UI
model. The main focus of XWT is SWT developer. It should be capable to do
what SWT can. So I think XWT should keep close as much as possible to SWT. 

 

Best regards

Yves YANG

  _____  

From: [email protected] [mailto:[email protected]] On
Behalf Of David Orme
Sent: Tuesday, January 27, 2009 9:04 PM
To: E4 Project developer mailing list; [email protected]
Subject: [e4-dev] Declarative UI in E4

 

Two things, by way of moving the discussion forward while the IP machine
grinds along:

(The impatient or overworked can read just the boldfaced text and get the
gist of what I'm saying. ;-)


Thing #1:)

My understanding is that our status is that Hallvard's code is making its
way through the IP Review process and onto the E4 server.

In the meantime, I had an idea that might unify the two current proposals.

(If I mis-characterize any of this, please correct me, but here is my
understanding of our current state:)

1) Hallvard's proposal is an XML layer on top of an EMF model that is
connected to the UI.

2) Yyves's proposal is to map XAML 1:1 to the SWT API.  He calls the
resulting API XWT.

Here's what I was wondering:  Yyves, would it be possible/desirable to make
XWT map 1:1 to Hallvard's EMF model rather than straight to SWT?  This seems
like it might be a sensible approach to unifying both proposals.

If the answer is "yes", I'd very much like to play with that and see what
the resulting code looks/feels like.


Thing #2:)

I've been thinking about the ways we have discussed for abstracting and
simplifying UI creation.  So far, we have only focused on XML
representation, but I recalled that Andy Maleh created (and proposed)
Glimmer, a JRuby-based UI DSL project.  And I've been interested in
translating Glimmer's ideas into Scala.

(I noticed that Boris invited Andy to participate over here, and
regrettably, he has not materialized yet.  Since I know Andy personally,
I'll reach out to him and invite him to join the conversation.)

In any case, I want to make sure that whatever we do does not preclude
Glimmer-like things in alternate JVM languages, whether JRuby, Scala,
JavaScript, etc.

In the abstract, it seems like it ought to be possible to map Glimmer(.JRuby
| .Scala) to EMF just like Hallvard maps XML to EMF.

Which brings me to my


Conclusion:)

Hallvard: Any ETA on when we will get to see your code at Eclipse.org?

I'd really like to get my hands on both of these proposals and play with
them. :-)


Best regards,

Dave Orme

PS: Andy: I've CC'd you on this mailing list message.  If you're interested,
please add yourself to the list so you can take part in the ongoing
conversation.  You know you're welcome here. ;-)



_______________________________________________
e4-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/e4-dev

Reply via email to