Hi Angelo, > I would like call about TK-UI for declarative UI but TK-UI use DOM and it seems that people prefer EMF than DOM.
So, two comments: 1) e4 is an incubator, and thus about exploring ideas and technology. I don't believe anything has been precluded. 2) I'm not sure there's a preference of EMF over DOM, or that the former precludes the latter for that matter. I mean really its just two ways of slurping data of disk and creating an in memory representation. Are these incompatible within the same running Eclipse? While its true that we're using EMF for the modelled UI work, I don't think EMF is viewed as the hammer for which everything must be a nail :) I think the roundup would be a great venue for you to talk about UFace. Regards, Kevin "Angelo zerr" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 11/04/2008 07:30 PM Please respond to E4 developer list <[email protected]> To "E4 developer list" <[email protected]> cc Subject Re: [eclipse-incubator-e4-dev] Fw: Declarative UI roundup? Hi Kevin, The subject is very interesting but I believe that Eclipse E4 have intention to use EMF. I would like call about TK-UI for declarative UI but TK-UI use DOM and it seems that people prefer EMF than DOM. I would like just say too, that I'm refactoring TK-UI to use UFace (where I'm contributing) which propose this project to Eclipse http://wiki.eclipse.org/Eclipse/Incubator/UFacekit I think that UFace is very interesting for declarative UI because : * it provide universal API to render it to SWT, Swing, QT, GWT... (UIElement ) * manage binding with JFace Databinding. So you can bind properties of widget (visible, text...), layout properties (orientation, with...) with anything. Into TK-UI it's easy to bind DOM element, attributes with tje UIElement. Each properties (ex : setVisible) notify listeners. * manage Databinding with UIForm. It's easy to manage master detail and into TK-UI I'm using to manage Databinding Expression Language (like XAML binding epression). Regards Angelo 2008/11/5 Kevin McGuire <[EMAIL PROTECTED]> Thanks all who responded to my previous note. As we did for the styling roundup, it'd be great if people could fill in a bit of information about a proposed technology as prep for us all for a call. At your earliest convenience, please take a moment to fill in an entry in the following table: http://wiki.eclipse.org/E4/DeclarativeUI/Declarative_Construction_Roundup You'll notice a striking resemblance to the styling one we did, about midway down http://wiki.eclipse.org/E4/DeclarativeUI/Styling_Roundup. The idea here is that providing the information shouldn't be laborious on the part of the presenter, but enough for everyone to get started investigating. We'll then have a bakeoff call, post slides and notes back to the wiki. We should aim to have the call in a few weeks. Best Regards, Kevin ----- Forwarded by Kevin McGuire/Ottawa/IBM on 11/04/2008 06:16 PM ----- Kevin McGuire/Ottawa/IBM 10/14/2008 05:49 PM To "E4 developer list" cc Subject Declarative UI roundup? Hi gang, As you may recall, in August we had a Styling roundup to look at the different available skinning technologies. While organizing it, we discussed also wanting to do one for declarative UIs. There was a lot of interest at the time, and there's been lots of discussion on this list lately about different declarative UI technologies/approaches. I think the Styling one went well so I was wondering if folks wanted to do one for declarative UIs? Seehttp:// wiki.eclipse.org/E4/DeclarativeUI/Styling_Roundup for an idea. This would involve some people volunteering to do a short presentation on a particular technology, either their own (e.g. XSWT) or one they are familiar with (e.g. XUL). There'd be some prep in putting a small amount of information on the e4 wiki, then a call with presentations. The idea is to have some decent content to discuss but not create a big presentation job for folks, so the emphasis would be on short presentations (and also out of the interest of keeping the call to say 1.5 hours which will be a challenge I think). The goals of the call would include but not be limited to: 1) All getting on the "same page" with respect to the different technology choices available to us. 2) Open discussion of pros/cons of different approaches. 3) What problems we believe it will solve in the e4 context. 4) Hopefully come away with a small number of "most promising" technologies which the community could focus on in e4. Any interest? Note that this is community driven content, so "yes" would mean "yes I'll sign up to provide some content". Regards, Kevin _______________________________________________ eclipse-incubator-e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev _______________________________________________ eclipse-incubator-e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
_______________________________________________ eclipse-incubator-e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
