Hi guys,

When I Googled for some smart way to implement pagination in
TurboGears today I was pleasantly surprised to see that the TurboGears
team had thought of that with the @paginate() decorator.

I implemented the pagination system easily but the URLs it provides
don't follow the Routes schema we've been working so carefully to set
up.  Routes lets you define a path (e.g., "/list/:page") and it will
pass the value of "page" to the controller method it's assigned to.
What I'd like to do is to take the value of the "page" variable and
from within the controller set the variable to some value and have
that end up as the page that the template displays.

I've tried setting numerous variables but all of them fail to tell the
template to use a specific page number.  Is there a magic trick or
does this pagination functionality assume you won't be using a tidy
URL schema?

Thanks in advance for all pointers, they're much appreciated.

Regards,
Friðrik Már


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to