Hi Keith,

I had, but I didn't want to use their bulky (and ugly) javascript for
what I was doing. I want to take advantage of the included prototype
functions (which that form validation class doesn't do at all).

Currently (to avoid a bulky client side javascript) the script applies
behaviours to each form on the page using prototype, and based on
class names, fires a JSON request (like the validation helper) but
makes the server do all validation ( that also means you only have to
define form validation stuff once). Simple validation like reg-ex'es
are handed client side, but I found it more powerful to include the
server validation that way you can include custom validators with
complex validation expressions... And this also means the client side
is much more light.

I guess I'm now looking towards just re-writing the symfony server
side form validation system so that it is standards compliant.

Thanks!


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony users" 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/symfony-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to