It is important to distinguish between display and functionality with forms. What I mean is, using the forms does not mean you have to render (display) them the way Django has it set up by default. I always use the Form API, and if I need custom validation on a field or the entire form, I override the appropriate clean method. I pass the widget argument if I want a different widget.
IMO, one of the best things about Django is the ease in which I can customize its parts but still leverage its functionality. On Wed, Dec 8, 2010 at 10:36 AM, christian.posta <christian.po...@gmail.com>wrote: > Do django developers use the Form API any time form elements need to > be displayed to users? Or do you just code the form yourself in the > templates and manually process them for smaller forms? > > In general, is it always better to use the Form API for any form you > display, regardless how simple, because of the built-in functionality > provided by django, or is it overkill? > > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
