I don't think it's goofy idea. Actually it is kind of what
dojo.validate.check() does: it takes a form id and a profile object, which tells
how to validate each field. Obviously the profile is generated by server
depending on underlying data types. Django has all information available to
generate it.
As I can see they support individual validations, some
dependency validations, equality validations (double checks), and
pre-filtering (e.g., trim whitespaces, upper/lowercase, and so on). So far it
fits Django like a glove.
Thanks,
Eugene
|
- Re: Django and AJAX: Setting aside the conflict Eugene Lazutkin
- Re: Django and AJAX: Setting aside the conflict Bill de hÓra
- Re: Django and AJAX: Setting aside the conflict David Ascher
- Re: Django and AJAX: Setting aside the conflict Robert Wittams
- Re: Django and AJAX: Setting aside the conflict Wilson Miner
- Re: Django and AJAX: Setting aside the conflict Pedro Furtado
- Re: Django and AJAX: Setting aside the conflict Amit Upadhyay
- Re: Django and AJAX: Setting aside the confli... Eugene Lazutkin
- Re: Django and AJAX: Setting aside the co... David Ascher
- Re: Django and AJAX: Setting aside the confli... Eugene Lazutkin
- Re: Django and AJAX: Setting aside the conflict Robert Wittams