Ivo, somehow I had missed the very start of the thread. I think that my
change pretty much implements the third alternative you describe in your
post, but for which you provided no patch (the one which defines the
variables at the top and bottom only, because I leave the if
index==first or
On Wed, Jun 13, 2001 at 04:28:12PM -0700, Jean Lagarde wrote:
Good day all,
Here is the original code, with my annotated change (I deleted an if test in
two places):
for index in range(first,end):
# preset
Title: RE: [Zope-dev] dtml-in batching improved
Back before the zope.org product directory became so easy to navigate I wrote an index
that I used to use which has batch links top and bottom:
http://www.zope.org/Members/haqa/productlist/view_source
Dunno if this helps...
Adrian
Nope, my solution used only one dtml-in and maybe a dtml-let, no
REQUEST
munging :-)
Ok, show me :)
Hurm... gimme a shout next Thursday when I have access to the code again
;-)
Actually, scratch that, check out the folder_contents.dtml file in
CMFDefault/skins of the CMF.
It does
Nope, my solution used only one dtml-in and maybe a dtml-let, no REQUEST
munging :-)
Ok, show me :)
Hurm... gimme a shout next Thursday when I have access to the code again ;-)
cheers,
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
On Thu, May 31, 2001 at 05:36:21PM +0100, Chris Withers wrote:
I've done it myself as well using (as described in the posting) two
dtml-in's (the second one purely for displaying the prev/next links).
Is your solution any different? (The only one I can think of is storing
the info in
When using batching in dtml-in, why is 'previous-sequence' only defined at
the first iteration of the current batch? And why is 'next-sequence' only
defined at the last iteration of the current batch?
I know this problem ;-)
I had it too, and stuck something in the collector about it. I did
On Wed, May 30, 2001 at 10:02:31PM +0100, Chris Withers wrote:
When using batching in dtml-in, why is 'previous-sequence' only defined at
the first iteration of the current batch? And why is 'next-sequence' only
defined at the last iteration of the current batch?
I know this problem ;-)
Ivo van der Wijk wrote:
On Wed, May 30, 2001 at 10:02:31PM +0100, Chris Withers wrote:
When using batching in dtml-in, why is 'previous-sequence' only defined at
the first iteration of the current batch? And why is 'next-sequence' only
defined at the last iteration of the current
I've done it myself as well using (as described in the posting) two
dtml-in's (the second one purely for displaying the prev/next links).
Is your solution any different? (The only one I can think of is storing
the info in your REQUEST object and using it later, but that's really
ugly.)
Hi all,
When using batching in dtml-in, why is 'previous-sequence' only defined at
the first iteration of the current batch? And why is 'next-sequence' only
defined at the last iteration of the current batch?
This behaviour makes it difficult to display a batch like this:
-- begin sample --
11 matches
Mail list logo
