Some more suggestions based on things that I have experienced while
recently making an application that required many forms based on
models:

- Ability to not display certain fields, mainly for when the value will
be post-filled in the view (i.e. the owner of an object being set to
the logged in user).

- Ability to override the default labels and help text, since in some
cases the labels and help text presented to an end user should not be
the same as what's seen in the admin interface (I believe the label
overriding was mentioned already, but help_text would be nice too).

- Speaking of help_text, it might be nice for the as_* methods to print
this out as well.

- Ability to add extra validation to form fields, above and beyond the
model's validation.  I think this would be satisfied with the
"formfield" parameter that Adrian mentioned.

These could be satisfied by adding more parameters taking <field name>:
<value> dictionaries.


--~--~---------~--~----~------------~-------~--~----~
 You received this message because you are subscribed to the Google Groups 
"Django developers" 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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to