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.
Everything works fine, but one line messes it up for me. self.items = list(self.collection[self.first_item-1:self.last_item]) Here it takes only the range from the passed array. My situation implies that I've already got full array fetched from the database, so I need it just to be left intact. so I changed it to self.items = list(self.collection) and it works like a charm. Not sure if it's worth including in the main trunk or I should just create my own version. Please consider this Thanks On Jul 9, 5:38 am, Ben Bangert <[EMAIL PROTECTED]> wrote: > On Jul 8, 2008, at 6:26 PM, Jose Galvez wrote: > > > Great Job Mike, webhelpers is a fantastic tool! > > But since you've removed the javascript stuff (which you really > > can't be > > blamed for, I can only imagine how hard it is to keep up with the > > moving > > target that is javascript libs) does anyone have a link_to_remote > > equivalent that works with jquery? > > The JS libs are definitely fast moving targets. I'm adding a > 'Snippets' section to the new PylonsHQ site, which I think would be a > great place to accumulate some recipes on common AJAX setups for > Pylons controllers and the JS for a specific JS lib that goes with it. > > Cheers, > Ben > > smime.p7s > 3KDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
