in AbstractChoice, i see now that localization of the "Choose One" string isn't a bug exactly, but i'm pretty bothered by the renderNullOption and emptyAllowed properties. the only issue to solve is whether null is an option and what to display if it's selected. these can both be solved at the same time (in a /much/ more efficient and less magical way) by simply having one property called nullDisplayString. if the value is non-null, then that string would be used as a choice and to display any selected null value. am i missing a case? in any case, right now, there is a resource lookup going on everytime a choice is rendered.
btw, is there anywhere else in the toolkit do we do magic lookups like this?
jon
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
