The same question was asked on stackoverflow: http://stackoverflow.com/questions/2303268/djangos-forms-form-vs-forms-modelform Its a good explanation - I liked the bit at the end: "The similarities are that they both generate sets of form inputs using widgets, and both validate data sent by the browser. The differences are that ModelForm gets its field definition from a specified model class, and so has methods that deal with saving of the underlying model to the database."
If you want to know *why* it was created, this post has some of the history: http://mirobetm.blogspot.com/2008/03/django-modelform-replacement-for.html (and there a number of others from other folk along the same lines) And, yes, reading more documentation (which, in the case of Django, is actually enjoyable) is a Good Thing. On Jan 31, 7:37 pm, hank23 <hversem...@stchas.edu> wrote: > I think I've read most of the documentation on Model Forms, but I > haven't seen much on how to customize them, other than changing the > order in which fields are displayed, or not displaying some fields at > all. The one ModelForm which I've done so far does not look very good > as it is automatically generated. If they can't be customized very > easily or very much then I'm not sure I see any big advantage in using > them as opposed to just using regular forms, that I can more easily > customize. Am I missing something or have I not read enough of the > documentation? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
