Re: Pager - return array rather than HTML..
| From: | Pierre-Alain Joye | Date: | Thu, 27 Jun 2002 15:01:30 +0000 |
| Subject: | Re: Pager - return array rather than HTML.. | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-7393@lists.php.net to get a copy of this message | ||
On Thu, 27 Jun 2002 16:00:19 +0100
Peter Bowyer <peter@mapledesign.co.uk> wrote:
> At 15:23 27/06/02 +0200, Tomas V.V.Cox wrote:
> >Take a look at the info returned by a simple call of:
> >
> >$data = DB_Pager::getData($from, $limit, $numrows, $maxpages = 4);
> >
> >Note that DB_Pager is "row" oriented instead of Richy's Pager which is
> >"page" oriented.
>
> Why do we have two pager classes?
At the release date of Pager, DB_Pager needed DB to work.
> I asked this question yesterday but
> didn't get any response, and your above comment is the first I've seen that
> points to any difference between the way the classes work.
Concurrent modules may be a good thing (like menu ;) ). May a merge could be a good thing too ?
pa