I think will_paginate is good stuff. Its simple and clean, and I’m
the support should be good since its from the err guys
I’d like now to turn your attention to a will_paginate rewrite I had made just recently:
Its not a drop in replacement, but core pagination had too much magic anyways…
It didn’t have too much magic, it had too little. It also had too complex API and internal structure. Also, like will_paginate, you always had more than one instance variable to pass around for a single paginated collection.
In my rewrite I eliminated the need for this by keeping all information in a single collection proxy instance. I also made it a bit more configurable and smarter than will_paginate.
My plugin also supports the ActionController::Base#paginate instance method and has unit tests. I have ported all core Pagination unit tests over to my plugin and it passes them all:
You can checkout the plugin from SVN and run unit tests without putting it inside an app. It will realize that and use rubygems instead. (BTW, uses sqlite.)
I can mimic the original Pagination API further, but I don’t know if that makes sense. Re-implementing its API would mean re-creating its cruft. I would rather work on more extensive test suite for the current functionality and improve view helpers for link rendering.
So, this plugin is - for now - as close as we can get to original Pagination. The question for all of you is: how close should we go? How much are we ready to break?