Jacob Kaplan-Moss wrote:
>>
>> I'm trying to figure out the case scenario where this becomes a useful
>> thing, and I couldn't find the mentioned documentation. Did I miss
>> it,
>> or does anyone have a good example where it is useful to have template
>> context as a stack?
>
> Well, the canonical example is ``{% for %}`` loops::
Another example is a generation of an output using subviews, which
require additional parameters. In this case parts of the template are
generated using some other views, and the result is passed in the main
view for an assembling. In this case it make sense to push parameters
for a subview before calling it, and pop them back, when it is done. In
short it is a very useful feature.
Thanks,
Eugene
PS: While in some cases it make sense to use custom tags to generate
complex parts of the template, imagine 5 such tags with 5 tag-specific
parameters --- you have to pass them all in your "super" template. It
becomes unmanageable very quick. There are cases when assembling the
output in a view method is simpler.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
