On 25 Aug 2003, Gisle Aas wrote: > Mark Stosberg <[EMAIL PROTECTED]> writes: > > > I would like to see an extension to this part of the interface which > > allows one to treat single and multiple SELECT lists the same way. In > > the current situation calling the same command can result in dealing > > with either the SELECT tag, or the OPTION tag, which I find less useful > > and confusing. > > But it is a model that give a uniform behaviour and interface for all > the inputs. I think this is a good thing and that it should be enough > to write better documentation that explains the mapping between the > HTML tags/elements and the HTML::Form input objects. As you > discovered it is not one-to-one when it comes to <select>. [...] > Since there is no representation of the <select> tag itself there is > no object to put this method on. [...]
FWIW, I found this part of the way HTML::Form works confusing too, and changed it in my port (well, quite a few other things have changed, so it's not a simple port any more). All 'controls' (in the HTML 4 terminology) are represented by single Control objects. Maybe the examples of the modified API here are of interest (in Python): http://wwwsearch.sourceforge.net/ClientForm/src/README-0_1_7b.html John
