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
"Yves YANG" <yves.yang@xxxxxxxxxxx> Sent by: e4-dev-bounces@xxxxxxxxxxx
02/02/2009 09:55 PM
Please respond to
E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>
[mailto:e4-dev-bounces@xxxxxxxxxxx] On Behalf Of Kevin McGuire
Sent: Tuesday, February 03, 2009 2:01 AM
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.
----- Forwarded by Kevin McGuire/Ottawa/IBM on 02/02/2009 07:41 PM -----
--- Comment #2 from Eric Moffatt <emoffatt@xxxxxxxxxx> 2009-02-02
15:47:51 -0400 ---
This makes perfect sense to me. We most certainly don't want the CSS to
against the 'focus' control but, as you say, the 'active part' (as defined
some higher level entity (aka the workbench)...
I'm all for having the Model/CSS boundary managed by a separate piece of
(bundle?), specific to this task. We should have enough information being
forwarded by the model to accomplish this fairly cleanly. This will allow
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