Comments on: jQuery Validation with Django Forms

By: Jacob

Jacob — Mon, 08 Mar 2010 21:22:02 +0000

Great idea, Dan. Unfortunately, I’m just not sure how reusable that wrapper would be. I find myself creating fields in so many different ways (templates, formsets with form_field_callback, etc) that I’d be lucky to use it 50% of the time. But the idea did come to mind while writing this, and your clarification makes me think that a generic ValidationForm superclass could handle the __init__ field class assignment.

By: Dan Ward

Dan Ward — Mon, 08 Mar 2010 20:28:13 +0000

Just to add, the wrapper method would run inside the form's '__init__' method, AFTER super'ing it.

Dan Ward: To prevent repeating yourself with the initial widget class attributes, it may be worth creating a wrapper, which iterates over each field, checking the required, max_length and min_length values, then applying the class respectively.

By: Dan Ward

Dan Ward — Mon, 08 Mar 2010 20:26:17 +0000

Nice guide, although may I add…

To prevent repeating yourself with the initial widget class attributes, it may be worth creating a wrapper, which iterates over each field, checking the required, max_length and min_length values, then applying the class respectively.

This way, you prevent the potential issue of having validation errors for data, which may, in fact be valid.

Of course, the other option is to output the field however you like and handle the form.fieldname.field.required (etc) attributes in the template and applying the class there.

Only a suggestion and I’m sure many will find the article very helpful

By: Jacob

Jacob — Mon, 08 Mar 2010 19:37:50 +0000

Thanks, I didn’t know about dajax.

By: gerardp

gerardp — Mon, 08 Mar 2010 19:27:03 +0000

Do you know dajax?
“easy to use AJAX libraries for django”

http://dajaxproject.com/