Eelco Hillenius wrote:
agree. but what we really want is a single model for dropdown choice values that is generic and can be easily extended.
That would be exellent!
Don't we have that more or less? The values are in a java.util.List (or collections) model.
That is ok for the simple things except the id/display value components. For that we need something else.
Of course we can also do it differently..
Just have the plain List or Collections inplace.
But add a method to the abstractdropdownchoice component:
addListRenderer(ListRenderer renderer)
then ListRenderer has +/- all the methods IIdList currently have like:
String getDisplayValue(Object) String getIdValue(Object) Object getObject(String,Collection)
This is how Swing renderers work now and i can also live with this kind of implementation.
johan
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
