On Apr 23, 8:52 am, xpanta <[email protected]> wrote: > Hi, > > I wanted to ask if I am somehow "obliged" to use the form class > provided by Django framework. I can see its use on "static" forms (eg. > registration forms or account forms) but most of the forms I write are > "dynamic" (forms that are dynamically created depending on the user, > whith input fields like <input type="text" > name="user_product_{{product_id}}">) > > I am new to Django, so I carry some old habits with me. Does the > django's form class provide solutions for more complicated forms? > Should I study it, further? > > Thanks, > Chris
You're not obliged to do anything, of course. But Django forms do give you a lot of useful functionality - easy ways to display fields, validate them, redisplay them with errors including the submitted values, automatically create/update model instances based on form values, etc. Why do you need dynamic fields with this particular pattern? What is that you want to achieve? Is this something that can be done with formsets? -- DR. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
