On Apr 1, 2006, at 3:39 PM, P T Withington wrote: Two questions to pursue: how different would this be from our current style feature? And: how different would this be from w3c css? I'm not sufficiently up to speed on either to be able to answer these questions without some research.
You mean the current compile-time CSS implementation?
No, I mean the simple tinting/styling feature we've had for a while. I think our goal with our current implementation is to be closer to w3c CSS, and this could help us get closer by providing cascading at runtime. (Obviously, for the DHTML back-end we can use the browser implementation of CSS and it will just be correct.)
Well, that's the question: does the cascade in CSS (at least avoiding the more exotic features in CSS2/CSS3 like first-word and first-line styles) align well with _javascript_ prototype inheritance? I'd like to assume it does, but didn't want to assume :-) It will mean a change from the current way we implement some features, such as text font/size/style, since they are presently individual attributes of text, not properties of a single style attribute.
Right. But there's a nice deprecation progression -- from duplication of state, to pure-virtual "forwarding" attributes using just a setter, to removing the attribute. In this case, I think it'd be worth the increased clarity and expressive power. |
_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
