But if you handle the pagination client sided and have a table with a bazillion of entries then all the entries will be downloaded to the client bit your client will probably never go beyond the first couple of pages.
Just think of this in a mail application where you are viewing a folder with 10k mails in it. In such cases I would really prefer some server side solution. Who ever implements painted cheekbones should consider this when doing his specific solution. Bye Norbert -- send by Samsung Galaxy Tab with Overcome Mod, so sorry for topposting. Am 20.10.2011 16:46 schrieb "CavalryJim" <[email protected]>: > > On Oct 19, 2:22 pm, mdfdroid <[email protected]> wrote: > > Ok so I solved my problem by creating two divs on the page. A table > > on the left that is paginated and has ajax search for assigning > > issues. Then another table on the right that just shows assigned > > issues. I have jquery watch for check box clicks and submit the > > form. The form is submitted remotely and just re renders the two > > divs. This way you can add issues by selecting them on the right, or > > remove them by unchecking them on the right. > > I had a similar problem with radio buttons and pagination. I used > jquery.dataTables to solve the problem. > With dataTables, you do not need will_paginate. The dataTable widget > handles all the pagination client side. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
