> in fact, select, choices (and radio) are still a weak part in wicket (imho). > there are many classes to deal with them, but most aren't customizable enough > and/or require different markup (span instead of select) as the designer would > put in.
It's certainly not a perfect framework, and we need people like you to point that out and come up with suggestions for improvement :) > especially for radiogroups or checkboxmulti it would be much easier to not > have > have a surrounding element, also options should be customizable from the > html... Tbh, I don't know these components well enough to have a strong opinion about it. What you can try though, is develop an alternative that you think would be better. Such a component could be placed in a wicket-stuff project (like minis), but if many people think this is a great improvement, it could even replace core components. Cheers, Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
