Hi Yves, That'd be a great demo to see at EclipseCon, it's a good idea. Will you have time to work on such a demo?
I think the issues in the bug thread are orthogonal though, since it's about the relationship between semantics in the workbench model and any form of declarative styling (ie. I assume it's the exact same problem for XWT integration). Regards, Kevin "Yves YANG" <[email protected]> Sent by: [email protected] 02/02/2009 09:55 PM Please respond to E4 Project developer mailing list <[email protected]> To "'E4 Project developer mailing list'" <[email protected]> cc Subject RE: [e4-dev] CSS + Modelled UI: Need notion of active part I think Declarative UI has more interaction with CSS. How about to start this integration with XWT + Modelled UI and prepare a nice demo together for EclipseCon? Best regards Yves YANG Soyatec - Eclipse OutSourcing & XAML for java http://www.soyatec.com Tel: +33 1 60 13 06 67 Mobile: +33 6 20 74 39 45 Fax: +33 9 58 07 06 67 From: [email protected] [mailto:[email protected]] On Behalf Of Kevin McGuire Sent: Tuesday, February 03, 2009 2:01 AM To: [email protected] Subject: [e4-dev] CSS + Modelled UI: Need notion of active part Eric suggested I forward this thread to the list. I think it's an interesting problem because it's about meta information expressed at the level of the workbench (active part), manifest as styling via CSS (as changes in tab colors), and how we should communicate that. Those interested should comment in the bug so we can keep the thread together. Regards, Kevin ----- Forwarded by Kevin McGuire/Ottawa/IBM on 02/02/2009 07:41 PM ----- [email protected] 02/02/2009 03:47 PM To Kevin McGuire/Ottawa/i...@ibmca cc Subject [Bug 263185] [CSS] Need notion of active part https://bugs.eclipse.org/bugs/show_bug.cgi?id=263185 Product/Component: E4 / UI --- Comment #2 from Eric Moffatt <[email protected]> 2009-02-02 15:47:51 -0400 --- This makes perfect sense to me. We most certainly don't want the CSS to be against the 'focus' control but, as you say, the 'active part' (as defined by some higher level entity (aka the workbench)... I'm all for having the Model/CSS boundary managed by a separate piece of code (bundle?), specific to this task. We should have enough information being forwarded by the model to accomplish this fairly cleanly. This will allow the us to freely 'play' with concepts in this area without affecting the other (non-CSS aware) parts of the code. We should perhaps take some time to discuss this on 'eclipse-e4'... -- Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You reported the bug._______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
