Inline. "Christopher Lenz" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > > I'd prefer a hybrid approach, where simple javascript validation checks > are generated, and the others are performed via AJAX callbacks.
+1. Well-known type validation and simple checks can be (and should be) done client-side. Complex validation should be: 1) done by server using callback from the client, server should specify which fields it wants to see 2) done by client using meta information provided by server > OTOH, the validation in this example would ideally not even get > triggered, because the date text field would be disabled until the > checkbox got checked :-P A better example is probably the classic > "matching passwords" validation. It is a good idea. I wonder if we have all info available to generate such code or a helper for such code. In one of my projects I didn't show form fields, which didn't make sense given user's input so far. It prevented user's confusing and reduced number of presented fields by 50-70% making the form compact and observable. I coded this code manually. It would be nice to automate it somehow. Thanks, Eugene