Ian, the only problem with that is that you need to know whether there
actually IS a previous or next object.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email t
you might want to do this 'work' when the user actually requests the page in question, not when you generate the one he is looking at.for example have 2 views defined in urls.pygetnext/(object-id)/getprev/(object-id)/and have these 2 views do the calculation on what is 'next' and issue the 301 redi
jcb wrote:
> I have a page that lists a bunch of Geolocation objects (using the
> generic view list, works great.) I have a detail page
> (django.views.generic.list_detail.object_detail) that works great the
> same way...displaying one geolocation (with a tiny Google map, nice.)
Perhaps the best
Okay, I've scoured the fine, fine documentation, and, well, nothing.
I have a page that lists a bunch of Geolocation objects (using the
generic view list, works great.) I have a detail page
(django.views.generic.list_detail.object_detail) that works great the
same way...displaying one geolocation
4 matches
Mail list logo
