On 5/9/07, Michael Koziarski <[EMAIL PROTECTED]> wrote: > > > > I think this is a two-step process. Step one is to just take exactly > > what's currently in Rails and bottle that up as classic_pagination or > > something like that. This will allow anyone using what currently is to > > migrate to Rails 2. Then, step 2 would be to improve on what is with a > > new plugin that can break backwards compatibility. > > We can even make the install hook for classic_pagination print a > warning that this code is a dead end and you should consider upgrading > to something with a vibrant future.
Those are great ideas! Pagination could be easily extracted from core as-is. (That's what I did with its unit tests before I refactored them.) Users should be warned that it has poor test coverage and that it's not going to be maintained. And as for "something with a vibrant future", errfree guys have just given me access to their will_paginate repo after we agreed to collaborate on making the next version of the plugin. We should quickly bring it up to full test coverage and enhance the API even further! Because there will be classic_pagination available I will simply drop support for the legacy API. One thing less to worry about :) -Mislav --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en -~----------~----~----~----~------~----~------~--~---
