On Oct 16, 8:29 pm, Jesse Young <[EMAIL PROTECTED]> wrote:
> My idea (implemented in my local version of Django) was to
> modify RegexURLResolver to return the urlpattern that was used, and
> store that (as well as the kwargs) as a property of the request.
>
> Does this seem like a useful patch? Or is there a better way to
> accomplish this?
I would love to see your implementation; it sounds like an
interesting, generic solution.
Comparing URL paths with regex is complicated and error-prone if you
have multiple levels of navigation, and setting a <body> class
requires huge, sprawling CSS selector stanzas that is hard to
maintain. The method I currently use is putting {% block
specific_section_name %} in all the navigation links to later override
with class="active" in specific templates, but that can be a lot of
typing, and can make for noisy templates, ugly HTML, and makes generic
templates more difficult.
- whiteinge
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
