On Wed, Jul 9, 2008 at 4:30 AM, Pavel Skvazh <[EMAIL PROTECTED]> wrote: > > I'd like to share a use case with paginate. > I've got a model that serves query results in the format I need. It > manages starts and limits, includes [totalrow] property so I just need > paginate to draw a nice paging bar.
If you find the navigator too restrictive, you can build your own in HTML and use the page.* attributes to look up the statistics. For instance, our users did not like the fact that the "next" link moves depending on the width of the page numbers and whether it's the first page. They preferred our older first/prev/next/last buttons and a little form to choose the page number. But the form had to provide a hidden parameter which I couldn't pass through .pager(). So I finally gave up on .pager() and made a custom navigator in a Mako function, which is nested inside my generic page function that takes a 'page' object. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
