-- Mark Maynereid <[EMAIL PROTECTED]> wrote (on Thursday, 06 December 2007, 07:34 AM -0800): > Thanks for that Matthew. Although it looks like it's still at rev 155 just > now.
My bad -- I committed to the original working repository I had, instead of the one in the laboratory. oops! Committed now, along with a few other minor sundries. > Matthew Weier O'Phinney-3 wrote: > > > > -- Mark Maynereid <[EMAIL PROTECTED]> wrote > > (on Wednesday, 05 December 2007, 07:47 PM -0800): > >> I seem to have a found a couple is simple bugs in revision 155. > >> Zend_Form_Element_Select and > >> Zend_Form_Element_Radio don't parse due to '.php' in the class > >> declarations. > > > > Oops! *notes to self: always check search and replace results carefully. > > > > Fixed in svn now. > > > >> On a more tricky issue I'm a little stuck dealing with form input > >> where the field is optional. I note your test.php contains > >> addValidator(new Zend_Validate_NotEmpty()) which is clear enough, but > >> how might I validate a Zend_Form_Element when the input is to be > >> considered optional for it? > > > > Ah -- missed that one. I've noted it as a required improvement; I'll let > > you know when this is possible in the laboratory code. > > > > You ask later in the email why the proposal isn't using > > Zend_Filter_Input. The primary reason is because I want the validators > > and filters attached to the individual elements; Zend_Filter_Input > > assumes you are going to validate multiple elements at once. By having > > the validators/filters per-element, we can utilize the same element in > > multiple forms. > > > > The downside, of course, is that there are some items such as marking > > elements as required/optional that have been achieved already in > > Zend_Filter_Input. I'll be looking closesly at that class as I finish up > > the prototype to make sure things are done in a compatible way. -- Matthew Weier O'Phinney PHP Developer | [EMAIL PROTECTED] Zend - The PHP Company | http://www.zend.com/
