the only point where DRY comes into play is when you're retrieving
data from the same view, is there a better way to make breadcrumbs?
On Sep 16, 2:40 pm, Maksymus007 <maksymus...@gmail.com> wrote:
> On Wed, Sep 16, 2009 at 10:53 PM, 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/b42d...
>
> > 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?
>
> > Thanks,
>
> > Jason
>
> DRY principle?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
