John reports: the current interface was undiscoverable for Tom Atlee. His answer was a link at the end that says, "see the next 20".

removing from 1.0. difficult, highly visible, and scores low on the posited priority scale.

  --Ethan McCutchen.....Wed May 06 10:46:43 -0700 2009

what are teh benefits of will_paginate?

  --Ethan McCutchen.....Tue May 11 14:28:24 -0700 2010

It was someone else who put "will_paginate" in the name of this ticket; vague memory is that it's some outside code thing that someone thought would be better, but I have no idea why.

  --John Abbe.....Wed May 12 19:36:13 -0700 2010

it's a rails gem. but I don't know what the costs/benefits are...

  --Ethan McCutchen.....Thu May 13 12:28:02 -0700 2010

I get that there is some dislike for the current interface, but I don't think there's been much discussion of what we want instead, just an idea about an implementation tool. not sure we're really ready to act on this...

  --Ethan McCutchen.....Thu May 13 12:29:17 -0700 2010

changed to idea.

  --Ethan McCutchen.....Thu May 13 12:30:26 -0700 2010

checking out the will_paginate screencast... http://railscasts.com/episodes/51-will-paginate

  --John Abbe.....Thu May 13 13:39:47 -0700 2010

I think Tom's lack of discovering the paging would be addressed by changing the arrows to "previous page" and "next page", which wouldn't even require will_paginate, right? I'm not into having more text on the page, but imho worth it if many people (and Tom's not exactly computer-illiterate) aren't going to get the arrows.

  --John Abbe.....Thu May 13 14:44:11 -0700 2010