> Why can't a form be instantiated automatically when passed a
> model (maybe with flags for which fields are enabled)? Or
> better yet, bind the form to a model (or model instance),

You mean like:

django.newforms.models.form_for_model
django.newforms.models.form_for_instance

I'm not sure where I stumbled across this first as I didn't find
it in the djangoproject.com docs, but it's clear that you're not
the only one to think this. :)

There is a separation (and so Django provides it) as you might
want a form that incorporates more or less than a model, but if
it's just a model that you want, these shortcuts eliminate some
of the grunt-coding.

> You could have a parameter for each model field like
> form=True or whatever if that field should be included in a
> form.

You don't get this much, but you at least get a shortcut for
building forms from a model/instance.  Additionally, modifying
the model would not be desirable, as you might want to have
different views/forms of the same model (and such tagging could
conflict).

-tkc




--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to