{hallmarks:text(multiselect) {label "Hallmarks"}
    {values "$hallmarks"}
    {options {{Scholarship 1} {Leadership 2} {Fellowship 3} {Service 4}} }
    {html {size 4}}
}

Hitting the submit button gets the multiply selected values of hallmarks through ad_page_contract, but then something seems to go amiss in ad_form. A ns_log entry down in the -new_data area (or -edit_data) shows that only the first selection appears in $hallmarks. Any additional selections are somehow lost.

I also tried replacing the {values "$hallmarks"} in the code snippet above with {values "1 2 3"}, with the same result: only the first value seems to make it into -new_data or -edit_data.

I grepped through the existing packages looking for some example code using ad_form with multiple selection, but I haven't found any.

Sorry for going on and on. I'm hoping that documenting my confusion will be useful to the folks working on ad_form documentation. If anyone has a working (even if ugly) example of using ad_form with multiselect, it would really help me to see one. Thanks in advance. :)

--Cathy

text(multiselect),multiple

Sorry about that but the form builder treats multiples as being different than other stuff and as ad_form is just wrapping the form builder with a (hopefully) more user-friendly API ...

ad_form is still a bit of an experiment...and the form builder incomplete.  Ideally ad_form (and the form builder) whould know that a "multiselect" datatype might return (will often return) mulitiple values.  But that's not the case, yet.  The form builder expects the programmer to tell it if this is true (silly since "multiselect" implies it) and ad_form blindly exports that API to you.

Obviously the whole form builder concept of a datatype needs to be extended so that our core code does what one expects, so that the form builder and ad_form follow the law of "least astonishment" when they take action.

I'm not quite sure when we'll get there.  Other core issues have seemed more relevant to me (non-scalability of permissions for instance.)  Others have picked up the slack in other areas, Peter in the APM (great work), Joel in documentation (ditto), Jeff in patch and release work (and Janine, too) and dozens of others in various subrealms of the project.

But we're getting to the point where "rapid development" is going to be a key concept, and cleaning up the form builder (and by inference ad_form) is going to be a top, top priority ...

I just want to let you know that I've got stuck by the same - how to call this? - feature, losing about two hours, because I first tried to understand the documentation. Also, the user-add.tcl page uses a "-query" feature in ad_page_contact that is not documented in 5.0.rc1.

Bests,
Frank

Randy