On 25 août, 23:40, Uwe Schuerkamp <uwe.schuerk...@gmail.com> wrote: > Hi folks, > > this posting sort of refers to my previous problem from last week as > I'm still working on the birdwatcher's site. I cannot wrap my head > around how to create intelligent navigation links from the current > context or http request.
(snip practical example) > I've played around with including > django.core.context_processors.request in my processors list which > results in the request.path variable being available, but I somehow > refuse to believe that this problem hasn't been solved before in some > clever, django-ish way. The problem is that there's no one-size-fits-all solution here - it's a reoccurring problem indeed, but it's somehow very application / project specific too. But anyway : there's just too much logic involved to implement this in the template itself, and that's certainly not something you want to manually handle in each and every view. I don't know enough about your project to provide a working OOTB solution, but given your example use case, I'd probably try to handle this in a middleware - process_view() seems like the right place -, with possibly some custom templatetag involved too. http://docs.djangoproject.com/en/1.2/topics/http/middleware/#writing-your-own-middleware HTH -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
