[Pmwiki-users] More on WikiTrail
Patrick R. Michaud
pmichaud at sci.tamucc.edu
Tue Nov 5 23:20:56 CST 2002
On 6 Nov 2002, John Rankin wrote:
> (Just joined the list) I like the idea of listing the stops in a
> vertical column, showing the current stop and the trail name. Look
> forward to seeing it. What happens if a page is on 2 trails or is
> this disallowed?
Multiple trails would be allowed but would be presented as multiple
menus, and also the wiki administrator would have to be fairly savvy about
being able to code it into the system. I'm not planning to do vertical
column display of trails with wiki markup--it'd have to be something
directly enabled in PHP/HTML by the wiki administrator (relatively easy
for one trail, more complicated for multiple trails).
> Pushing my luck: would it be useful if on the page specifying the list of stops the author could choose to show (say) the first sentence / 15 words of fame or whatever from the stop page?
Yes, you might be pushing your luck. :-) But I'd say even this is possible
as a customization, if we define a special markup for it (the "T:stop" markup
you suggested might work). But I feel a "slippery slope" here again;
after having the first few words of text from the target page, folks will
want to be able to add date/time of last revision for the target page, and
we start getting into weird markup details again. I might code up a
sample add-on script just to show how it could be done, but it would likely
be a per-wiki customization and not anything that ever evolved to be a
PmWiki "standard feature".
Also, in converting T:stop to :stop:text, would we need to strip out
the markup from the target page? I would think so, but am curious as to
what you had in mind there...
> I can't help feeling that ideally, the chosen mark-up would ensure a
> trail knows its pages *and* a page knows its trail.
Well, the existing implementation has this, -except- that it's possible for
the trailpage to know about pages that don't have the trail markup, and it's
possible for other pages to have the trail markup without being listed on
the trailpage. I think that what you're really saying is that there needs
to be synchronization between the trailpage and the pages on the trail, and
I don't see a way of doing this without changing PmWiki's file structure,
directly modifying wiki page contents, and/or performing text searches
through multiple trail pages.
Having PmWiki automatically add trail links if the reader followed
a trail link to arrive at the current page might work, but it kinda bugs
me that someone arriving at the same page via a non-trail link doesn't see
that the page is part of a trail. So I'm not entirely comfortable with
the auto-trail-generation approach, even though I have a few ideas about
how it might be implemented. A few real-world examples of where it's really
needed or would be used would really help (see PmWikiPhilosophy #3:
implement features in response to specific needs).
I'm planning to spend another day or so cleaning up my existing trail.php
add-on script a bit and then I'll release it for others to experiment with
in their own wiki sites.
More information about the pmwiki-users