public
Description: Adaptive pagination plugin for web frameworks and other applications
Homepage: http://github.com/mislav/will_paginate/wikis
Clone URL: git://github.com/mislav/will_paginate.git
Click here to lend your support to: will_paginate and make a donation at www.pledgie.com !
commit  27c2e5b4fa34a76b52d6a394780bc503abca7e20
tree    dbe2f75c9bdc3bebf39f0da2f02109d2be1b55fa
parent  34749e01c706e28760c75fb92950f3568cb4252a
name age message
file .gitignore Sun Apr 06 20:02:06 -0700 2008 test with rcov and bring it up to 100% test cov... [mislav]
file .gitmodules Sun Dec 21 09:11:25 -0800 2008 website -> gh-pages folder [mislav]
file CHANGELOG.rdoc Sun Jan 11 20:40:52 -0800 2009 Total rdoc love. Point out that this is framewo... [mislav]
file LICENSE Sun Jan 11 20:40:52 -0800 2009 Total rdoc love. Point out that this is framewo... [mislav]
file README.rdoc Thu Mar 26 16:57:41 -0700 2009 fix grammar in credits [mislav]
file Rakefile Fri Nov 06 16:48:46 -0800 2009 delete .manifest file, crazy .autotest monkeypa... [mislav]
file init.rb Sun Apr 06 20:57:03 -0700 2008 add CHANGELOG covering the 2.2.0 release [mislav]
directory lib/ Loading commit data...
directory spec/
submodule website - f6fd277 Thu Jan 08 15:29:56 -0800 2009 delete stuff in examples/ as they're now GitHub... [mislav]
file will_paginate.gemspec Fri Nov 06 16:48:37 -0800 2009 change WillPaginate::VERSION to "3.0.pre"; clea... [mislav]
README.rdoc

The will_paginate Ruby library

Pagination is just limiting the number of records loaded and displayed. Why should you let it get in your way while developing?

This is how you paginate on an ActiveRecord model:

  Post.paginate :page => 1, :order => 'created_at DESC'

Most of the time it’s as simple as replacing "find" with "paginate" and specifying the page you want.

Some resources to get you started:

I’m not using Rails; can I still use will_paginate?

Absolutely — although will_paginate started off as a Rails plugin, now it is a completely framework-agnostic library with support for Rails and Merb built-in. The core library doesn’t have any dependences and you can safely use it in any Ruby code.

When will_paginate is loaded in an environment where ActiveRecord and ActionView are present, it automatically hooks into these frameworks to provide easy pagination on your models and in your views. The same mechanism works for Merb applications, too. But, if no known framework is present then you have absolute control over what parts of will_paginate do you want to load and where you want them mixed in.

Installation

The recommended way is that you get the gem hosted on gems.github.com:

  gem install mislav-will_paginate

In Rails 2.1, add a gem dependency:

  # for Rails 2.1 and newer
  config.gem 'mislav-will_paginate', :lib => 'will_paginate', :version => '~> 3.0'

If you’re using Rails 2.0 or older, or any other Ruby framework, just add a simple require to a file that initializes your application. For example, in Rails you would put this at the end of "config/environment.rb".

  gem 'mislav-will_paginate', '~> 3.0'
  require 'will_paginate'

That’s it. Remember to install the gem on <strong>all</strong> machines that you are deploying to.

There are extensive installation instructions on the wiki.

Example usage

Typical usage involves a paginating find in the controller:

  @posts = Post.paginate :page => params[:page], :order => 'updated_at DESC'

It’s true: paginate works just like find — it just doesn’t fetch all the records. Don’t forget to tell it which page you want, or it will complain! Read more in WillPaginate::Finders.

Render the posts in your view like you would normally do, and when you need to render pagination, just stick this in:

  <%= will_paginate @posts %>

You’re done. Read more in WillPaginate::ViewHelpers::Base.

How does it know how much items to fetch per page? It asks your model by calling its per_page class method. You can define it like this:

  class Post < ActiveRecord::Base
    self.per_page = 50
  end

… or don’t worry about it at all. WillPaginate defines it to be <strong>30</strong> by default. You can always specify the count explicitly when calling paginate:

  Post.paginate :page => params[:page], :per_page => 50

The paginate finder wraps the original finder and returns your result set that now has some new properties. You can use the collection as you would use any other array. WillPaginate view helpers also need that collection object to be able to render pagination:

  <ol>
    <% for post in @posts -%>
      <li>Render `post` in some nice way.</li>
    <% end -%>
  </ol>

  <p>Now let's render us some pagination!</p>
  <%= will_paginate @posts %>

Authors and credits

The original author of will_paginate was PJ Hyett, who later handed over development to Mislav Marohnić. (The library was completely rewritten since then.)

All these people helped making will_paginate what it is now with their code contributions or just simply awesome ideas:

Chris Wanstrath, Dr. Nic Williams, K. Adam Christensen, Mike Garey, Bence Golda, Matt Aimonetti, Charles Brian Quinn, Desi McAdam, James Coglan, Matijs van Zuijlen, Maria, Brendan Ribera, Todd Willey, Bryan Helmkamp, Jan Berkel, Lourens Naudé, Rick Olson, Russell Norris, Piotr Usewicz, Chris Eppstein, Brandon Arbini, Denis Barushev, Paul Barry, Ben Pickles, Ken Collins, Lida Tang and Pieter Noordhuis.

Usable pagination in the UI

There are example CSS styles to get you started on the will_paginate project page.

More reading about pagination as design pattern:

Want to discuss, request features, ask questions? Join the Google group.