> If you look at the CSS 3 draft, you'll see the editors have included support
> for namespaces. And they're pretty simple. Basically it goes like
>
> @namespace blah "ms.allman.blah"
>
> blah|MyBlahComponent {
> name: value
> }
>
> You can also define a default namespace like this:
>
> @namespace "org.apache.pivot.wtk"
That is interesting. I could see a case for adding support for this.
> Not sure why we couldn't just add a dep for a binary jar like CSSParser.
Two reasons:
1) Licensing. Any binaries we depend on have to have a license that is
compatible with the ASL.
2) We have thus far tried to stay away from introducing external dependencies.
When you download Flex, you get everything you need out of the box. There is no
list of additional libraries that you have to download in order to use it
(aside from the dev environment, of course). We want users to have a similar
experience with Pivot.
> It could even be optional. "If you want's CSS support, you need to include
> the CSSParser jar file on the classpath."
It's not optional if the platform code depends on it, though.
> Flex makes no assumption about where the stylesheets live. You tell it with
> a <Style src="asasd.css"/> tag in your mxml file.
As I have previously mentioned, if an appropriate CSS serializer is written,
you could do the same in BXML:
<bxml:include bxml:id="foo" src="foo.css"/>
> Personally, I don't care if Pivot can automagically find my style sheets or
> not. If it can be done really well, then by all means. But otherwise, I
> don't mind typing something like <Styles src="asd.css"/>
Again, it comes back to a question of how those styles are associated with
component instances. In previous emails, I have explained some of the
challenges behind supporting this in BXMLSerializer.
