<div class="gmail_quote">On Fri, Feb 13, 2009 at 9:45 AM, Hans <span dir="ltr"><<a href="mailto:design5@softflow.co.uk" target="_blank">design5@softflow.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>Friday, February 13, 2009, 7:42:44 AM, Peter wrote:<br>
> On Fri, Feb 13, 2009 at 7:40 AM, Peter Bowers <<a href="mailto:pbowers@pobox.com" target="_blank">pbowers@pobox.com</a>> wrote:<br>
<br>
</div><div>> Since pagelist already supports a count=21..40 type of syntax, what does the<br>
> start= parameter add?<br>
<br>
</div>It adds convenience. It makes it easier to set a pagelist chunk. You<br>
just need to calculate the start value, and supply the count value.<br>
So it simplifies the math involved.<br>
<br>
It will still not be easy to construct a dynamic link navigation<br>
like (Go to page 1 2 3 ....)<br>
within a custom template. But it just may be possible.<br>
<br>
For a general breakpagelist recipe I think we still require an<br>
additional pagelist to supply the pagelist count, which the script<br>
will use to calculate the range parameters for the actual pagelist<br>
(the one which produces formatted output).<br>
<div></div></blockquote><div><br>While the math could get a bit inconvenient I think that complexity can entirely be hidden within the code and leave the pagelist parameter set unchanged... I guess I'm assuming a page editor is not going to be specifying a given "chunk-page" -- they will just indicate somehow within their pagelist that they want it to be "chunked" and from there on they will click on a link... Is that right? <br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div>
>><br>
>> I think all that's needed is this line:<br>
>><br>
>> $FmtV['$AllMatchCount'] = count($matches);<br>
>><br>
>> But this must occur *before* $opt['count'] processing.<br>
>><br>
>><br>
> Hmmm... In retrospect maybe this line should occur at the end of<br>
> MakePageList() so that any other FPL functions can depend on it as well...<br>
<br>
> (BTW I'm not picky on the name of the variable -- $AllMatchesCount or<br>
> $AllMatches or $PageListCount or whatever. I just think it would be good to<br>
> differentiate between $MatchCount which respects the count=x..y and this new<br>
> variable that doesn't respect that parameter.<br>
<br>
</div>I suggested $FmtPV['$PageListCount'] = $PageListCount;<br>
I am not picky on the name either, but I thought we need a PV for use<br>
in a pagelist template.</blockquote><div><br>That makes sense to me to have it as a PV. I think I'd still lobby for something related to the already-available $MatchCount or else change $MatchCount from FmtV to FmtPV (Or add $FmtPV['$ThisMatchCount'] or the like) -- just for consistency's sake. <br>
</div><div><br>-Peter <br></div></div>