Just chiming in, To clarify, I only have two patches regarding pagination: - #2575 fixes up some of the messy bits (including a few bugs) and adds orphaning. - #2576 makes a PaginatorPage object which is useful for self-contained pages (IMO usual use on a template)
> Trying to account for everybody's particular > preferences for representing page numbers for "other pages", etc, > becomes tricky. When I last looked at Chris's enhancement, it wasn't > immediately clear to me how to resolve all those problems. Neither of my patches address this (nor make it any more of a problem than it is now). On a side note, the one thing I dislike about the current paginator (and my reason behind PaginatorPage) is that is seems very un-encapsulated when it hits the template. I'd rather have one 'paginator' key in my context (a PaginatorPage object) than having a myriad of related keys: 'paginator_current_page', 'paginator_has_next_page', 'paginator_batch_size', ... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
