On Thu, Sep 17, 2009 at 4:53 AM, neri...@gmail.com <neri...@gmail.com> wrote:
>
> Is there any benefit to using {% url %} other than retrieving data
> from the same view? I was looking for a better way to make a
> breadcrumb menu than hard wiring the urls into every page and came
> across the {% url %} tag and this post:
>
> http://groups.google.com/group/django-users/browse_thread/thread/b42d814e8f52b89a/45cf75b352c709b0?lnk=gst&q=breadcrumb#45cf75b352c709b0
>
> It makes sense to me to use {% url %} in order to retrieve data form
> the same view but if you have to pass {% url %} a specific view then
> what's the difference than hard wiring a url?
The biggest reason to use {% url %} is to defend yourself against
changes in URLpattern structure. For example, if you change the URL
pattern for your login view from:
url(r'^/user/login/$', login_view, name='login_view')
to
url(r'^/login/$', login_view, name='login_view')
you need to modify every template that references "/user/login/".
However, any reference to {% url login_view %} will be automatically
updated to point at the new URL.
It's also a big part of building reusable apps - if you use {% url %}
in your templates, you don't need to worry about where in the URL tree
your app has been deployed - you just reference the view by name, and
the URL will be resolved to wherever it has been mounted.
Yours,
Russ Magee %-)
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
