Django Aware - Latest Comments in Digg Style Pagination In Django Revisited

Re: Digg Style Pagination In Django Revisited

MeowCode — Sat, 26 Sep 2009 09:30:25 -0000

Ook, it's here:
http://www.meowcode.com/dja...
I tried to make it step-by-step, let me know how does it works for you in comments there.

Re: Digg Style Pagination In Django Revisited

MeowCode — Fri, 25 Sep 2009 12:12:43 -0000

Glad to hear you like it, I'll publish it in next few days and link back here..

Re: Digg Style Pagination In Django Revisited

john — Thu, 24 Sep 2009 20:27:03 -0000

gamejumble

Wow, I love the result.

I'd love to use this but can't figure out how to get it working. Could you post a complete example, eg view, url, template + any thing else necessary.

Thanks

Re: Digg Style Pagination In Django Revisited

MeowCode — Sun, 20 Sep 2009 09:39:59 -0000

You can see final result of pagination with alternative CSS here:
http://www.gamejumble.com/c...

Re: Digg Style Pagination In Django Revisited

MeowCode — Sat, 19 Sep 2009 20:08:26 -0000

Thanks for sharing your work, here are fixes of the code:
1) Code as-is will not run with Apache/WSGI, because wsgi does not allow writing to stdout. To fix this, remove 'print' statements in code.
2) If you add:
view = template.resolve_variable(self.view, context)
to PaginationNode.render(), you will be able to pass 'current_url' as context-variable also, similary to page index
3. As meppum posted, using alternative template/css is very good idea

Re: Digg Style Pagination In Django Revisited

corsairmoran — Sun, 13 Sep 2009 01:33:08 -0000

Please post a sample urls.py and views.py

Re: Digg Style Pagination In Django Revisited

rollenc — Wed, 26 Aug 2009 12:07:27 -0000

Greate script

Thanks

Re: Digg Style Pagination In Django Revisited

john — Sat, 15 Aug 2009 04:02:54 -0000

I'd also like to see an example, surprising there isn't one in the first place.

"No messy URLs to configure" how do you pass the page no without configuring the url?

Re: Digg Style Pagination In Django Revisited

pkenjora — Wed, 22 Jul 2009 20:19:07 -0000

Wow a bit harsh on the delivery but I'm not opposed to pointing users at something better.

I looked over the other code and it looks good. Go for it... sorry my startup has taken time away from my ability to maintain this code, a year is a good run though.

PS: The frustrated user above doesn't sound like he/she even tried the code before passing judgment. I hope I'm wrong.

Re: Digg Style Pagination In Django Revisited

frustrateduser — Wed, 22 Jul 2009 18:27:27 -0000

For anyone wanting to do pagination and sorting I suggest using:

http://code.google.com/p/dj...
and
http://code.google.com/p/dj...

DO NOT WASTE YOUR TIME trying to understand this templatetag.
It might actually work well, but with practically no documentation and no complete examples you're bound to loose a lot of your valuable time.

Re: Digg Style Pagination In Django Revisited

guest — Tue, 30 Jun 2009 18:37:00 -0000

Could you post an example of how you pass current_page to views.py?

Thank you.

Re: Digg Style Pagination In Django Revisited

Olejek Rokitnikowy — Wed, 17 Jun 2009 03:32:42 -0000

The thing I like most with that kind of design is when you can just type in the page number and it takes you there. If you need to click 20 times to get from page 1 to page 70 it's just too much trouble and often not worth it.

Re: Digg Style Pagination In Django Revisited

meppum — Mon, 18 May 2009 15:32:32 -0000

I prefer this pagination over the alternatives.

I posted a modified version of the pagination.html that can be used with any of the css files from here: http://mis-algoritmos.com/2...

You can find the modified version of pagination.html here: http://meppum.com/media/blo...

Re: Digg Style Pagination In Django Revisited

Red Wine — Wed, 06 May 2009 12:49:29 -0000

Usually if you post the specific problem in the comments you'll get one of the awesome readers to drop by with an answer.

Re: Digg Style Pagination In Django Revisited

UnhappyJoe — Wed, 29 Apr 2009 23:01:09 -0000

While I accept that you are not obligated to do any of this for free, and that your code is very good, I can't help but feel like you're passing the buck when you tell me I should change my URLs. One of the main selling points of django is its extensibility, and I think it would be fitting for you to make changes to your script so that it can be used in a wider range of situations, rather than just the situations which suit you.

I have eliminated querystrings from my application where possible, but when it comes to searching I would actually prefer a query string.

You suggested changing my URL to:

{% paginate "site/search/bla/all/2days/" items current_page 50 10 paged_items %}

But how exactly is that going to work? How is "site/search/bla/all/2days/" going to insert the parameters specified by the user doing the search? ie..

site/pictures of cats and dogs/bla/videos-only/2weeks

............

There absolutely must be a simple way to modify your script to support any kind of url, and I guess I am forced to find it myself and modify your script. I shall post the results here when I get around to it.

All that aside, thanks for your effort. I'm in a better position with your code than I would be without it, so for that I am grateful.

Re: Digg Style Pagination In Django Revisited

pkenjora — Wed, 29 Apr 2009 12:09:42 -0000

Try changing your URL to the following:

{% paginate "site/search/bla/all/2days/" items current_page 50 10 paged_items %}

The current page you will still have to carry around in the context. Pete's comment below is addressing this I think.

Not sure how much experience you've had passing parameters via URL but its a very powerful tool in Django.

Re: Digg Style Pagination In Django Revisited

Pete — Wed, 29 Apr 2009 10:18:58 -0000

Brilliant! Works a treat.

I'm trying to get the pagination widget to display in one template block and the page data to display in another template block.

Is there a way to share the "variable" of paged data across two blocks easily or do I need to create some sort of global in the paginaton tag and pass that across to the context of the other block?

Great work.

Re: Digg Style Pagination In Django Revisited

UnhappyJoe — Mon, 27 Apr 2009 20:03:12 -0000

I apologise for my previous comment... but you DO need some documentation he he. For somebody who has only recently picked up Django, your code made very little sense to me to begin with :)

I am trying to use your pagination code on a search page.. so I need this sort of thing -

site/search/?s=bla&show=all&threshold=2days&page=3

Is this possible using "a resolve context variable call" (don't know what that is) ?

Re: Digg Style Pagination In Django Revisited

pkenjora — Mon, 27 Apr 2009 11:34:07 -0000

Sorry to hear that, guess I can't please everyone all of the time. You may want to double check the code, it supports dynamic URLs.

{% paginate "[dynamic URL here]" items current_page 50 10 paged_items %}

If you're asking for variable defined URLs then I suggest adding a resolve context variable call around the URL variable. Next release i guess.... hopefully your head will feel better by then.

PS: Note I didn't ask, "Why would you need dynamic pagination URLs..."

Re: Digg Style Pagination In Django Revisited

UnhappyJoe — Mon, 27 Apr 2009 06:05:35 -0000

I gotta say, you fail at documentation.

After an hour or two of slamming my head into my desk, I finally realised that the idea of this is to have the paginator do all the paging for you [including the ORM calls]. Then I realised your /strict/url/s are not actually suitable for my paged search page and I'm going to have to modify it anyway.

Would have been so much easier for you to explain how it works, than it was for me to spend time discovering it's not what I'm looking for.

Re: Digg Style Pagination In Django Revisited

miami web design — Thu, 16 Apr 2009 05:28:59 -0000

If you want to use this script you need to remember to put a scrolldown list with all the pages too. I'm sick and tired of going for example from page 200 to 400 and having to reload the site like 50 times because it only moves 4 pages at the time.

Re: Digg Style Pagination In Django Revisited

meppum — Wed, 15 Apr 2009 20:45:55 -0000

One of the main reasons to use urlpath/p/ over ?page=p is caching. The built in django cache only caches by the part of the url that comes before the parameters. So it would consider www.foo.com/?page=1 the same as www.foo.com/?page=2.

Re: Digg Style Pagination In Django Revisited

Yehat — Tue, 07 Apr 2009 08:37:49 -0000

Paul,

Thanks for the update...

I found that by putting href="?page={{ page }}" in the pagination.html file instead of
href="/{{ pagination.view }}/{{ page }}/" you omit the need to include the url path as an argument... this is especially helpful if you are looking at, say, a list of Y's that are related to the Nth X object. This way the dynamic path (e.g. path/XN) can be omitted. It would otherwise have to be passed into the template by the view.

What were the reasons you chose to the convention urlpath/p/ over the convention ?page=p ?

I'm a Django newbie ;p

Re: Digg Style Pagination In Django Revisited

pkenjora — Mon, 06 Apr 2009 10:49:16 -0000

Yehat,

I've updated the post with more details. Hope it helps. What were you having trouble with? Usually if you post the specific problem in the comments you'll get one of the awesome readers to drop by with an answer.

- Paul

Re: Digg Style Pagination In Django Revisited

Yehat — Mon, 06 Apr 2009 08:33:29 -0000

Paul,

If you want to help people, as I'm sure you do... more detailed documentation is required... especially for newbie Django peeps.