[pmwiki-users] Re: Re: Re: Useful default pages (was: Profiles.HomePage)

[Martin Fick]

On Tue, Dec 13, 2005 at 01:23:43PM -0600, Patrick R. Michaud wrote:
> On Tue, Dec 13, 2005 at 01:57:18PM -0500, Martin Fick wrote:
> > 
> > but you lead me to suggest a new tag called  (:trailist :) 
> > which acts just like pagelist in a page except that trails
> > know to look for it and insert the output into the list at
> > the current location?
> > 
> >   This would allow me to have pagelists and traillists mixed
> > on a trail page.  The pagelists would be ignored when
> > getting the pages in the trail, but the traillists would be
> > included.
> 
> It took me a bit to figure out what "trails know to look for
> it" was supposed to mean -- but I think that you're suggesting 
> that we have a (:traillist:) analog to (:pagelist:), and the ReadTrail
> function is able to look for (:traillist:) on a trail index page
> and fill in the appropriate items.  

  Yes, that's what I meant, sorry.


> Could work, although I think
> that grabbing (:pagelist:) would be just as good.  I'm not aware
> of many instances where it'd be important to distinguish them.

  I think that's what the recipe does.  I was simply
suggesting the alternative markup since it would be less
intrusive than the current recipe.  I figured that might be
the reason the current recipe is not in the core since it
seems like a nice feature to have.

  I agree that having pagelist processed this way would be
nice, but it does seem like there should be a way to turn it
off for a specific pagelist?  Maybe an -notail option or maybe
simply indenting it?



> It also seems like it would not be too difficult to get a
> 
>    <<|(:pagelist ...:)|>>
> 
> markup to work, although it's not clear to me what should be displayed in
> between the two |...|'s for the trail.  Maybe it's just empty in that case,
> so that we get
> 
>     << PreviousPage | NextPage >>

  I think the recipe does this already, as you suggest,

  -Martin