Duplicate functionality

You want him to join forces with himself on Custom Pagers? :)

Michelle

Previous/Next API provides no user-facing functionality, just a pair of function calls to pull up the previous and next node ID in an arbitrarily defined list. Although some folks have made good use of it, it doesn't provide enough functionality (in my opinion) to introduce a dependency.

On the flip side, Custom Pagers is a swiss army knife intended for people who need to slice and dice complicated argument driven views and navigate through them. The flexibility it offers comes at the price of more confusing configuration and severe performance penalties -- with large lists of nodes, Custom Pagers simply crashes sites on small servers.

Flippy is a "turn it on and forget it" module with some themability. It has no dependencies, makes relatively efficient queries to build its pager, and that's all it does. Combining it with Custom Pagers would mean writing two separate approaches to paging and combining them in a single module for no reason other than namespace purity. I'd prefer the simplicity of pointing people with simple needs to a simple module, and those with complex problems to a more customizable solution that they understand the need for.

Keeping track of this thread

Hi Eaton. So should we consider this a successor to Custom Pagers as far as Drupal 7 is concerned? I'm working on moving my d6 site over d7 and I use Custom Pagers quite a lot -- if Flippy works as a replacement that's one less thing I need to wait for.