Re: Using CSS for XML Events

>If it is indeed the case that there is a particular handler that is
>generic and rich to justify being wired up to lots of different
>elements on a page, --say the squishyButtonWithPoorResponse example,
>we need to ask if it makes more sense to create an XML element 
>in the language in question that does the requisite wiring under the
>hoods, rather than smatter class or idref attrs all over the page.

I thought about that before making my first post, and it occurs to me then
why do we need CSS then?

IMU, the reason is not burdening the content tree model markup with
orthogonal issues, such as style or behavior.

Conceptually only, I think behavior is dynamic style, so appropriate as
extension under CSS module.  However, I have no qualms with making a "CES".

XML is general enough to do an infinite variety of things, just as any
language can, but that doesn't mean we should do all of them.  I think the
separation of tree from style and behavior is very important, and even wish
it was required, not just encouraged.

IMHO, one of the biggest challenges with standards right now, is there are
only a very few who implement them.  Or you may view that as an advantage,
until you want to standardize something that users need, but browser
vendors want to keep proprietary.  It is the law of supply and demand at
work.  So IMO, a primary goal is to simplify the parsing, etc..  Strict
XMLis a good step...

-Shelby Moore

Received on Monday, 16 December 2002 16:46:36 UTC