On Fri, 2006-08-04 at 21:50 -0700, bernie2004 wrote:
> when using a generic views object_list,
> i would like to know if there is a faster way to get all
> the extra variables inside a custom template tag:
>
> {% navigation pages page has_previous has_next %}
>
> and
>
> @register.simple_tag
> def navigation( pages, page, has_previous, has_next ):
> ... create some navigation code here ...
> ... return navigation code ...
>
> do work but i would prefer something like
>
> {% navigation context %}
>
> and
>
> @register.simple_tag
> def navigation( context ):
> ... create some navigation code here ...
> ... return navigation code ...
>
> which doesn't and i wonder if there is something i could do to simplify
The simple_tag shortcut is only for really simple tags. You've moved
beyond that a little (since "context" isn't a template variable).
Fortunately, writing a normal template tag is simple and that will give
you full access to the context. Your case should be very easy, because
it seems like you don't even need to process arguments to your tag.
Try something like this:
class Navigation(Node):
def render(self, context):
# create navigation code.
# access context as a dictionary (context['pages'], etc)
...
return result
def navigation(parser, token):
return Navigation()
register.tag(navigation)
Here, the Node class is from django.template. Any string you return from
the render method will be inserted into the template.
This gives you a tag you can call as
{% navigation %}
(no variables required).
Regards,
Malcolm
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
