Re: [Wicket-user] Adding Support for

[Igor Vaynberg]

any feedback on this yet? if not, i guess i will polish it with its current feature set and that will be that.

-Igor

On 11/23/05, Andrew Berman <[EMAIL PROTECTED]> wrote:

I should've known........

On 11/23/05, Igor Vaynberg < [EMAIL PROTECTED]> wrote:

your wish is my command. now you just have to wait a few hours until anon cvs syncs.
-Igor

On 11/23/05, Andrew Berman < [EMAIL PROTECTED]> wrote:

I won't be able to give it a shot until it works with HEAD as I've made the switch already and am using 1.2 specific stuff.  Once it is compatible with HEAD, I'll check it out.....

--Andrew

On 11/23/05, Igor Vaynberg < [EMAIL PROTECTED]> wrote:

just checked in my first pass at this so you guys can check it out and give me feedback. i had to check it into wicket_1_1 branch because component reference doesnt work in head yet. i also put the new components into extensions because the core is getting too crowded imho. if people want me to move it into core we can discuss that separately. the components are in wicket.extensions.markup.html.form.select package.  and the examples are in component reference on the bottom of the form section.

these components give you pretty much total control of how the select/option/optgroup tags are rendered. there is a convinience SelectOptions class that will create a quick list of options like the current choice components do. this one uses IOptionRenderer instead of IChoiceRenderer since it uses the actual model object instead of a string id. see the examples.

-Igor

On 11/22/05, Mark Derricutt < [EMAIL PROTECTED]> wrote:

Something along those lines yeh.

On 11/23/05, Igor Vaynberg < [EMAIL PROTECTED]> wrote:

so you want to specify the optgroup tags in your model? something like
class Category { String name; List choices }

and provide List<Category> as the model? so that the name of categories become optgroup tags?