Hi David, The latter. Here's the e4 summit page, although I'm not sure how much it helps:
http://wiki.eclipse.org/E4/DeclarativeUI What we're looking at is declarative technology as another way to build UIs in the Eclipse platform. At the CSS level, this would be a CSS parser to read in the CSS files, likely some SWT support so the styles would be applied directly to the widgets on creation, an approach to mapping CSS concepts like ID, Class, pseudo class, to Eclipse concepts, understanding the role of JFace in all this, etc. Other related declarative technologies worth considering are XForms for building wizards/dialogs/editors/etc. although I suspect our plates will be full just looking at CSS technology. This initial effort is really around CSS enabling technologies but other declarative approaches are worth considering at this early juncture. We haven't yet discussed editing environments or tooling. It'd be great if you could at some point present the CSS Editor in WTP. Perhaps we could do it sometime after this first technology evaluation? That would seem to dovetail nicely. Hope that clarified. I know its tough keeping up with all the conversations. Cheers, Kevin David M Williams <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 06/24/2008 03:14 AM Please respond to E4 developer list <[email protected]> To E4 developer list <[email protected]> cc Subject Re: [eclipse-incubator-e4-dev] CSS and declarative UI round up I realize that me not knowing exactly what you are asking for doesn't bode well :) ... but, what does this encompass? CSS Editing? or, more a CSS Rendering Runtime? If the former, I'd like the CSS Editor in WTP considered and would be happy to present., if there's interest. Thanks, From: Kevin McGuire <[EMAIL PROTECTED]> To: E4 developer list <[email protected]> Date: 06/23/2008 02:59 PM Subject: [eclipse-incubator-e4-dev] CSS and declarative UI round up Hi folks, Over the course of discussions, many folks have come forth with a favorite CSS/ declarative-UI implementation. So much to choose from! So much to know! As a first step, I thought it'd be helpful for us to have a roundup of them all so we can discuss their pros and cons. Eventually we'd all like to see some working CSS code in e4 eclipse.org repo and at the moment it seems the main problem is we have too many to choose from (a great problem to have!). What I had in mind was: Those who have some technology they'd like to bring forth prepare a small presentation of its pros and cons. We have a call where they are presented. We can as a group then better understand our requirements and which technologies fit those. Ideally we would have three presentations of 1/2 hour each (including discussion), plus wrap up discussion, so two hours max for the call. I'd prefer a shorter call but I don't think that's realistic. If we have more than three presentations then we can split it into two calls, since I don't know about you but my attention span nears zero after 2 hours. Our goals should be selecting the technology which will be the initial commit for the purpose of investigation. We may change our minds later, but we need to start with something. If there are two (or more) favorite technologies we can commit both, like we have the EMF/non-EMF modelling work. What do folks think? If we like this approach, I'd suggest we aim for a call in approximately two weeks, to folks time to prep. 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
