tonemcd wrote:
>I don't understand why a more generic form of this tag isn't available;
>
>{% datatofillinthetemplate "templates/macrosnippet.html" %}
>
>Is there a philosophical reason why this doesn't exist
>
>
Inclusion tag doesn't always just renames context vars. It can (and very
often does) some simple logic which can't be included in a template
syntax. Consider an example of a form field widget that accepts three
optional args and then does some preprocessing kung-fu:
@register.inclusion_tag('artist_widget.html')
def artists(data={}, errors={}, suggest_list=[]):
data=data.copy()
if data.has_key('artists') and type(data['artists'])==str:
data['artists']=[data['artists']]
return {
'data':data,
'errors':errors,
'suggests':suggest_list,
'js_url':settings.JS_URL,
'style_url':settings.STYLE_URL,
}
I bet no template author will want to deal with things like distinction
between a string and a list with this string :-)
And for the simple cases making such a template tag is in my opinion
simple enough. Too many helpers that simplify simplified simple things
are bad :-).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
