agnostic-will_paginate 3.0.0

data/.autotest

@@ -0,0 +1,54 @@
+Autotest.add_hook :initialize do |at|
+  
+  at.libs = 'lib:spec'
+  
+  at.clear_mappings
+  
+  at.add_mapping(%r{^lib/will_paginate/(.+)\.rb$}) { |_, match|
+    "spec/#{match[1]}_spec.rb"
+  }
+  at.add_mapping(%r{^spec/.+_spec\.rb$}) { |f, _| f }
+  at.add_mapping(%r{^spec/(finders/activerecord_test_connector.rb|database.yml|fixtures/.+)$}) {
+    'spec/finders/active_record_spec.rb'
+  }
+  at.add_mapping(%r{^spec/((spec_helper|shared/.+)\.rb|spec.opts)$}) {
+    # simply re-run all specs
+    at.files_matching %r{^spec/.+_spec\.rb$}
+  }
+  
+  # add these to ignore list
+  %w{ .git test/ rails/ Rakefile README.rdoc init.rb .autotest
+      doc/ coverage/ LICENSE CHANGELOG .manifest will_paginate.gemspec examples/
+      spec/tasks.rake spec/console spec/rcov.opts
+    }.each { |path| at.add_exception path }
+  
+end
+
+Autotest::Rspec.class_eval do
+  # RSpec guys forgot about `libs` in make_test_cmd
+  def make_test_cmd_with_libs(files_to_test)
+    make_test_cmd_without_libs(files_to_test).sub(' -S ', " -S -I#{libs} ")
+  end
+  
+  alias :make_test_cmd_without_libs :make_test_cmd
+  alias :make_test_cmd :make_test_cmd_with_libs
+  
+  # ugh, we have to monkeypatch Autotest ...
+  # the regexp it generates for the exception list just matches too much
+  # 
+  # SOLUTION: wrap it up in another regexp that anchors the whole expression to
+  # the beginning of the path
+  def exceptions
+    unless defined? @exceptions then
+      if @exception_list.empty? then
+        @exceptions = nil
+      else
+        # old (BAD):
+        # @exceptions = Regexp.union(*@exception_list)
+        @exceptions = /^\.\/#{Regexp.union(*@exception_list)}/
+      end
+    end
+
+    @exceptions
+  end
+end

data/.gitignore

@@ -0,0 +1,4 @@
+/doc
+/rails
+*.gem
+/coverage

data/.gitmodules

@@ -0,0 +1,3 @@
+[submodule "website"]
+	path = website
+	url = git@github.com:mislav/will_paginate.git

data/.manifest

@@ -0,0 +1,61 @@
+.autotest
+.gitignore
+.gitmodules
+.manifest
+CHANGELOG.rdoc
+LICENSE
+README.rdoc
+Rakefile
+init.rb
+lib/will_paginate.rb
+lib/will_paginate/array.rb
+lib/will_paginate/collection.rb
+lib/will_paginate/core_ext.rb
+lib/will_paginate/deprecation.rb
+lib/will_paginate/finders.rb
+lib/will_paginate/finders/active_record.rb
+lib/will_paginate/finders/active_record/named_scope.rb
+lib/will_paginate/finders/active_record/named_scope_patch.rb
+lib/will_paginate/finders/active_resource.rb
+lib/will_paginate/finders/base.rb
+lib/will_paginate/finders/data_mapper.rb
+lib/will_paginate/finders/sequel.rb
+lib/will_paginate/version.rb
+lib/will_paginate/view_helpers.rb
+lib/will_paginate/view_helpers/action_view.rb
+lib/will_paginate/view_helpers/base.rb
+lib/will_paginate/view_helpers/link_renderer.rb
+lib/will_paginate/view_helpers/link_renderer_base.rb
+lib/will_paginate/view_helpers/merb.rb
+spec/collection_spec.rb
+spec/console
+spec/console_fixtures.rb
+spec/database.yml
+spec/finders/active_record_spec.rb
+spec/finders/active_resource_spec.rb
+spec/finders/activerecord_test_connector.rb
+spec/finders/data_mapper_spec.rb
+spec/finders/data_mapper_test_connector.rb
+spec/finders/sequel_spec.rb
+spec/finders/sequel_test_connector.rb
+spec/finders_spec.rb
+spec/fixtures/admin.rb
+spec/fixtures/developer.rb
+spec/fixtures/developers_projects.yml
+spec/fixtures/project.rb
+spec/fixtures/projects.yml
+spec/fixtures/replies.yml
+spec/fixtures/reply.rb
+spec/fixtures/schema.rb
+spec/fixtures/topic.rb
+spec/fixtures/topics.yml
+spec/fixtures/user.rb
+spec/fixtures/users.yml
+spec/rcov.opts
+spec/spec.opts
+spec/spec_helper.rb
+spec/tasks.rake
+spec/view_helpers/action_view_spec.rb
+spec/view_helpers/base_spec.rb
+spec/view_helpers/link_renderer_base_spec.rb
+spec/view_helpers/view_example_group.rb

data/CHANGELOG.rdoc

@@ -0,0 +1,105 @@
+== "agnostic" branch
+
+* added Sequel support
+* added an initialization hook for Merb
+* refactored URL generation
+* BACKWARDS INCOMPATIBLE: refactored LinkRenderer; also markup changes
+    <span class="current">1</span> is now <em>1</em>
+    a.prev_page -> a.previous_page (for consistency)
+* "prev_label" -> "previous_label"
+* ported view tests to specs
+* setup Autotest
+* added per_page=(limit) attribute writer to set default per_page
+* Remove :include option from count_all query when possible (Rails 2.1)
+* added WP::ViewHelpers::ActionView and LinkRenderer
+* specs for ViewHelpers::Base and LinkRendererBase
+* created LinkRendererBase that implements windowed visible page numbers logic
+* created WP::ViewHelpers::Base abstract module that implements generic view helpers
+* ported finder tests to specs
+* added WP::Finders::DataMapper
+* added WP::Finders::ActiveRecord mixin for ActiveRecord::Base
+* created WP::Finders::Base abstract module that implements generic pagination logic
+* removed dependency to ActiveSupport
+
+== 2.3.1, released 2008-05-04
+
+* Fixed page numbers not showing with custom routes and implicit first page
+* Try to use Hanna for documentation (falls back to default RDoc template if not)
+
+== 2.3.0, released 2008-04-29
+
+* Changed LinkRenderer to receive collection, options and reference to view template NOT in
+  constructor, but with the #prepare method. This is a step towards supporting passing of
+  LinkRenderer (or subclass) instances that may be preconfigured in some way
+* LinkRenderer now has #page_link and #page_span methods for easier customization of output in
+  subclasses
+* Changed page_entries_info() method to adjust its output according to humanized class name of
+  collection items. Override this with :entry_name parameter (singular).
+    
+    page_entries_info(@posts)
+    #-> "Displaying all 12 posts"
+    page_entries_info(@posts, :entry_name => 'item')
+    #-> "Displaying all 12 items"
+    
+== 2.2.3, released 2008-04-26
+
+* will_paginate gem is no longer published on RubyForge, but on
+  gems.github.com:
+  
+    gem sources -a http://gems.github.com/  (you only need to do this once)
+    gem install mislav-will_paginate
+    
+* extract reusable pagination testing stuff into WillPaginate::View
+* rethink the page URL construction mechanism to be more bulletproof when
+  combined with custom routing for page parameter
+* test that anchor parameter can be used in pagination links
+
+== 2.2.2, released 2008-04-21
+
+* Add support for page parameter in custom routes like "/foo/page/2"
+* Change output of "page_entries_info" on single-page collection and erroneous
+  output with empty collection as reported by Tim Chater
+  
+== 2.2.1, released 2008-04-08
+
+* take less risky path when monkeypatching named_scope; fix that it no longer
+  requires ActiveRecord::VERSION
+* use strings in "respond_to?" calls to work around a bug in acts_as_ferret
+  stable (ugh)
+* add rake release task
+
+
+== 2.2.0, released 2008-04-07
+
+=== API changes
+* Rename WillPaginate::Collection#page_count to "total_pages" for consistency.
+  If you implemented this interface, change your implementation accordingly.
+* Remove old, deprecated style of calling Array#paginate as "paginate(page,
+  per_page)". If you want to specify :page, :per_page or :total_entries, use a
+  parameter hash.
+* Rename LinkRenderer#url_options to "url_for" and drastically optimize it
+
+=== View changes
+* Added "prev_page" and "next_page" CSS classes on previous/next page buttons
+* Add examples of pagination links styling in "examples/index.html"
+* Change gap in pagination links from "..." to
+  "<span class="gap">&hellip;</span>".
+* Add "paginated_section", a block helper that renders pagination both above and
+  below content in the block
+* Add rel="prev|next|start" to page links
+
+=== Other
+
+* Add ability to opt-in for Rails 2.1 feature "named_scope" by calling
+  WillPaginate.enable_named_scope (tested in Rails 1.2.6 and 2.0.2)
+* Support complex page parameters like "developers[page]"
+* Move Array#paginate definition to will_paginate/array.rb. You can now easily
+  use pagination on arrays outside of Rails:
+
+    gem 'will_paginate'
+    require 'will_paginate/array'
+    
+* Add "paginated_each" method for iterating through every record by loading only
+  one page of records at the time
+* Rails 2: Rescue from WillPaginate::InvalidPage error with 404 Not Found by
+  default

data/LICENSE

@@ -0,0 +1,18 @@
+Copyright (c) 2009 Mislav Marohnić
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of 
+this software and associated documentation files (the "Software"), to deal in 
+the Software without restriction, including without limitation the rights to 
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of 
+the Software, and to permit persons to whom the Software is furnished to do so, 
+subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all 
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS 
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR 
+COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER 
+IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN 
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.rdoc

@@ -0,0 +1,125 @@
+= 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:
+
+* The {will_paginate project page}[http://mislav.github.com/will_paginate/];
+* Your mind reels with questions? Join our {Google group}[http://groups.google.com/group/will_paginate];
+* {How to report bugs}[http://github.com/mislav/will_paginate/wikis/report-bugs];
+* {Watch the will_paginate screencast}[http://railscasts.com/episodes/51] by Ryan Bates.
+
+== 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 <em>completely
+framework-agnostic</em> 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}[http://gems.github.com/]:
+
+  gem install mislav-will_paginate
+
+In <b>Rails 2.1</b>, 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.
+
+<i>There are extensive {installation
+instructions}[http://github.com/mislav/will_paginate/wikis/installation] on {the
+wiki}[http://github.com/mislav/will_paginate/wikis].</i>
+
+
+== 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:
+
+* {Pagination 101}[http://kurafire.net/log/archive/2007/06/22/pagination-101];
+* {Pagination gallery}[http://www.smashingmagazine.com/2007/11/16/pagination-gallery-examples-and-good-practices/] featured on Smashing Magazine;
+* {Pagination design pattern}[http://developer.yahoo.com/ypatterns/parent.php?pattern=pagination] on Yahoo Design Pattern Library.
+
+Want to discuss, request features, ask questions? Join the {Google
+group}[http://groups.google.com/group/will_paginate].

data/Rakefile

@@ -0,0 +1,58 @@
+require 'rubygems'
+begin
+  hanna_dir = '/Users/mislav/Projects/Hanna/lib'
+  $:.unshift hanna_dir if File.exists? hanna_dir
+  require 'hanna/rdoctask'
+rescue LoadError
+  require 'rake'
+  require 'rake/rdoctask'
+end
+load 'spec/tasks.rake'
+
+desc 'Default: run specs.'
+task :default => :spec
+
+desc 'Generate RDoc documentation for the will_paginate plugin.'
+Rake::RDocTask.new(:rdoc) do |rdoc|
+  rdoc.rdoc_files.include('README.rdoc', 'LICENSE', 'CHANGELOG.rdoc').
+    include('lib/**/*.rb').
+    exclude('lib/will_paginate/finders/active_record/named_scope*').
+    exclude('lib/will_paginate/finders/sequel.rb').
+    exclude('lib/will_paginate/view_helpers/merb.rb').
+    exclude('lib/will_paginate/deprecation.rb').
+    exclude('lib/will_paginate/core_ext.rb').
+    exclude('lib/will_paginate/version.rb')
+  
+  rdoc.main = "README.rdoc" # page to start on
+  rdoc.title = "will_paginate documentation"
+  
+  rdoc.rdoc_dir = 'doc' # rdoc output folder
+  rdoc.options << '--inline-source' << '--charset=UTF-8'
+  rdoc.options << '--webcvs=http://github.com/mislav/will_paginate/tree/master/'
+end
+
+desc %{Update ".manifest" with the latest list of project filenames. Respect\
+.gitignore by excluding everything that git ignores. Update `files` and\
+`test_files` arrays in "*.gemspec" file if it's present.}
+task :manifest do
+  list = `git ls-files --full-name -x *.gemspec -x website`.chomp.split("\n")
+  
+  if spec_file = Dir['*.gemspec'].first
+    spec = File.read spec_file
+    spec.gsub! /^(\s* s.(test_)?files \s* = \s* )( \[ [^\]]* \] | %w\( [^)]* \) )/mx do
+      assignment = $1
+      bunch = $2 ? list.grep(/^(test|spec)\//) : list
+      '%s%%w(%s)' % [assignment, bunch.join(' ')]
+    end
+      
+    File.open(spec_file, 'w') { |f| f << spec }
+  end
+  File.open('.manifest', 'w') { |f| f << list.join("\n") }
+end
+
+task :website do
+  Dir.chdir('website') do
+    %x(haml index.haml index.html)
+    %x(sass pagination.sass pagination.css)
+  end
+end

data/init.rb

@@ -0,0 +1 @@
+require 'will_paginate'

data/lib/will_paginate.rb

@@ -0,0 +1,45 @@
+require 'will_paginate/deprecation'
+
+# = You *will* paginate!
+#
+# First read about WillPaginate::Finders::Base, then see
+# WillPaginate::ViewHelpers. The magical array you're handling in-between is
+# WillPaginate::Collection.
+#
+# Happy paginating!
+module WillPaginate
+  # This method used to hook in ActiveRecord and ActionView at load time,
+  # but now doesn't do anything anymore and will be removed in future releases.
+  def self.enable
+    Deprecation.warn "WillPaginate::enable() doesn't do anything anymore"
+  end
+
+  # Enable named_scope, a feature of Rails 2.1, even if you have older Rails
+  # (tested on Rails 2.0.2 and 1.2.6).
+  #
+  # You can pass +false+ for +patch+ parameter to skip monkeypatching
+  # *associations*. Use this if you feel that <tt>named_scope</tt> broke
+  # has_many, has_many :through or has_and_belongs_to_many associations in
+  # your app. By passing +false+, you can still use <tt>named_scope</tt> in
+  # your models, but not through associations.
+  def self.enable_named_scope(patch = true)
+    return if defined? ActiveRecord::NamedScope
+    require 'will_paginate/finders/active_record/named_scope'
+    require 'will_paginate/finders/active_record/named_scope_patch' if patch
+
+    ActiveRecord::Base.send :include, WillPaginate::NamedScope
+  end
+end
+
+if defined?(Rails)
+  require 'will_paginate/view_helpers/action_view' if defined?(ActionController)
+  require 'will_paginate/finders/active_record'    if defined?(ActiveRecord)
+end
+
+if defined?(Merb::Plugins)
+  require 'will_paginate/view_helpers/merb'
+  # auto-load the right ORM adapter
+  if adapter = { :datamapper => 'data_mapper', :activerecord => 'active_record', :sequel => 'sequel' }[Merb.orm]
+    require "will_paginate/finders/#{adapter}"
+  end
+end