On Mar 23, 10:32 pm, Ian Bicking <[EMAIL PROTECTED]> wrote: > These can't be that hard, can they? If they are hard, then we could > push a little something back into FormEncode, I suppose. If these are > easy, then not using @validate should be easy, as it's the second two > items that I think people are more likely to want to override:
I think they're fine being part of validate... i just think that validate should be compartmentalized... use kwargs or something to split that out. tangentially... something i dislike in the current 'validate' system is how it only supports 1 form. in a framework i built under mod_perl a few years back, calls to ( what essentially were ) form_result, form_error and form-generation would accept 1 or 2 args. with 1 arg, it would use form['_default'] , with 2 , it would access a named form. it was really useful on multi-form pages ( which i did a lot of ) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
