Le 22/05/2011 22:21, Gregor Müllegger a écrit :
{% renderform my_form %}
Another suggest from formrenderingtools...
Can we consider that "form" is the naming convention for form context variables?
* generic views use "form"
* there is usually only one form in a view
If "form" can be considered as a convention, could we apply "convention over
configuration" here?
::
{% renderform %}<!-- equivalent to {% renderform form %} -->
Convention: use the "form" variable
Configuration: pass my_form as an argument
In formrendering tools, there are 2 kinds of context:
* form context: where a "form" variable is required in the context => form,
field list, form errors...
* field context: where a "form" variable is useful, and a "field" variable is
required => label, field errors, field, widget...
Benoît
--
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.
