It is nice to know I'm not the only one struggling with DropDownChoices. I'm new to Wicket and I'm pretty far with rebuilding an application we are using internally. Has anybody proposed an alternative or a wrapper to DropDownChoices?
Vitaly Tsaplin wrote: > > The DropDownBox component is in fact well designed in theory. But I > think the way it works is a bit inconvenient in practice. Normally the > main purpose of this component in to supply some value or an index for > a model but a label is needed only for to be presented to a user. > Unfortunately we are supposed to use either the same value (a string > representation) for both pupposes or to use some kind of a wrapper and > to pollute the model by some strange "SelectOption" object even though > that the model would normally accept an integer. > > Vitaly > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/DropDownChoice-getting-value-into-the-model-tp15905486p15907346.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
