My reasoning for using `style` rather than `css`: you control it with a `<STYLEsheet>`. Flex calls this concept `STYLEname`. HTML calls this concept `Class selector`. I realize that we are implementing the CSS specification, but I can't find any precedent for calling this selector a `CSS class`.
On 2010-08-24, at 13:21, Max Carlson wrote: > I'm still for CSS/cssclass since we're not just talking about styles, but > cascading stylesheets it feels more descriptive. But I'll be happy either > way! > > Regards, > Max Carlson > OpenLaszlo.org > > On 8/23/10 4:21 PM, P T Withington wrote: >> I'm working on implementing http://jira.openlaszlo.org/jira/browse/LPP-7358 >> >> We want to be able to use the concept of CSS classes (quite different from >> LZX classes) to style LZX nodes. We want to be able to write style rules >> like: >> >> .foo { backrgound-color: blue } >> >> In HTML, you assign CSS classes to your<div> by: >> >> <div class="foo" ... >> >> In which case the above selector would apply to the div. >> >> --- >> >> In LZX, the word 'class' is already heavily overloaded, so we want to come >> up with a more expressive name for this feature. In the bug we initially >> proposed: >> >> <view cssclass="foo" ... >> >> and then proposed: >> >> <view styleClass="foo" ... >> >> I lean toward naming this new class property `styleclass`, in keeping with >> the other LZX built-in properties being all lower case, and in keeping with >> the `value="$style{...}"` constraint and the `<attribute >> style="background-color"` syntax. In our implementation, you will be able >> to use a space-separated list of classes, so that you can have several >> different class selectors apply at once, just as in true CSS. >> >> Comments?
