1) I used the names getValue/setValue mainly because the code is derived from alike methods in qForms. Would it make more sense to use a single method--like fieldValue() (although I'm not sure I like that name?)
I like the idea of a single name for both get/set because it fits well with the jQuery model. I would opt for a new method name so that existing methods can be deprecated and eventually removed. This is why I'm not a big fan of overriding "val". I think it's too ingrained at this point and a behavior change would be trouble. Even though the return type would be the same, the return value would not (or might not).
2) If you use an array to set the value on a text field, what value should we put in? Only the first position? Do we concatenate the array and use that value?
Good question! :-)
I'd probably start w/the methods that manipulate select elements (moving option elements around, transferring them to another select element, doing n-related select boxes, etc.)
Yes. Sam Collett has some great option utilities as well, and they're already jQuery plugins. That would be worth looking into. Mike
