Karl,
As a part-time backender with far more front-end experience, I want to
vote in favor of using className. That references back to the property
as it is used in ECMA-script as well as steering clear of the mistaken
impression that is for use primarily with styles. This wasy it'll be
quite understandable by front-end web-developers and really keeping good
form.
Karl von Randow wrote:
Thanks,
Yes, attributesText remains so you can work it both ways :) There's even an
attributes map that takes names and values.
I did notice that struts used styleClass. I based className on other
implementations with the same problem, it seems to be a bit of a defacto
standard:
http://www.mozilla.org/docs/dom/domref/dom_el_ref4.html
http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/classna
me.asp
I think it is a case of 'no way to do it'. The <jsp:useBean> tag just
tantalises us :)
Note I've had to use className instead of class because you can't use
"class" as a taglib property. Does anyone know any different on that?
It would be neat to not have to use className!
<snip/>
Unfortunately, there may not be a way to do that. As a data point, the
Struts html taglib uses styleClass.
--
( /' _/_ __ _ _
|/|///)(/(/(//_(-/
_/
Phone: +31 (0)297-283665
E-mail: [EMAIL PROTECTED]
Website: http://www.windgazer.nl
"The trouble with doing something right the first time, is nobody
appreciates how difficult it was."
-- Unknown Artist
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
