Eelco Hillenius wrote:
is it a joke ? In that case web design templates would need a unique
class attribute for each element that is going to be used via Ajax.
And in some cases it's not possible at all. For example, odd rows in a
table might have a different color than even rows. Typically one kind of
rows have the same class attribute.
If wicket will use class attribute as an identifier then there will be
no way to work with table rows.
He said that as a user. The Wicket framework won't switch to using
classes instead of ids of course :-)
Eelco
Phew, I also read that the wrong way. It'd been interesting to see
though how you'd manage to keep Ajax working and all. Outputting the
java class as html class might be nice though. It would be useful to
style wicket components in css. But it's easy to do this yourself already.
Matthijs
--
Matthijs Wensveen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
