On 11/10/05, Sean Cazzell <[EMAIL PROTECTED]> wrote: > Now in your kid template you have paginator.has_next, > paginator.has_previous, etc. The paginator.page_range function will let > you do lists of available pages like gooooooogle does on large search > results :)
These are cool features. I think I like the decorator suggestion, because it can automatically manage the incoming request parameters. I'm somewhat torn about that, though, because explicitly naming the parameters for the page position doesn't require guesswork on the part of the user. I'd be interested in hearing more opinions about decorator (with implicit request parameters) as in Leandro's message and independent entity as in Sean's message. > I stole this idea from Django - I have actually ported/stolen a lot of > things from Django (some generic views, get_object_or_404, timesince, > etc) to TurboGears. I'd like to hear more about these things. Kevin
