On Jul 12, 12:31 pm, André Eriksson <ean...@gmail.com> wrote:
> Good proposal overall. One thought I have in order to try and combat
> the massive parameter list of {% form %} is to optionally add an
> ending tag, as well as sub-tags:
>
> {% form myform %}
> {% using birthday=calendar %}
> {% renderer "as_ul" %}
> {% autocomplete "name_autocomplete" %}
> {% doctype xhtml1 %}
> {% endform %}
>
I'm +1 on Russell's proposal in general but I'm also -1 on the big
parameter list to the proposed {% form %} tag. Having written some
complex form field rendering tags for extjs/sencha I can say that
without some kind of built-in *args/**kwargs-like parameter handling
for template tags, then having more than a handful of parameters gets
long and messy quickly. Also, it doesn't make your tag that user
friendly either when they have to keep referring to the docs to figure
out how to use it.
Andre's idea is interesting and is certainly more readable.
regards
Matthew
--
http://wadofstuff.blogspot.com/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@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.
