>
> {% formconfig widget widgets.Textarea for "comment" %}
> {% formconfig row using "forms/rows/ul.html" %}
>
> The first statement instructs the form to use a textarea widget for any
> formfield named "comment." The second instructs the form to use ul's as the
> default formrow template anytime a {% formrow field %} is encountered.
>
I agree in {% formconfig %} being magical. Having "widget" "row" modes
feels a bit limited and it seems unnatural to have a template change
it's syntax based on a keyword. It feels more natural to have two
separate templatetags for each behavior, but we don't want to
introduce more complexity.
It is still not clear to me about the "widget" mode, is the second
parameter a import path? I think it would be clearer to include a
template path just like "using" instead of a import path that the
designer is not aware of.
{% formconfig widget "forms/widgets/textarea.html" for "comment" %}
or even
{% formconfig widget "comment" using "forms/widgets/textarea.html" %}
in order to mantain the same syntax for {% formconfig %}.
Is it possible for a django user to overload {% formconfig %} to do
something else? or do we have to wait for a next Django release to
have new behavior?
What about an "errors" mode? or a "help text" mode. I can see why it
would be handy to be able to extend it according to developers needs.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en.
