--
ColasNahaboo - 11 Sep 2002
Useful idea -- as hierarchically minded self I have a hard time to completely abondon "classical" order in favor of the
C2:WikiWay

However, unclassically, I don't like more and more tags
When you scan the pages to find out about the hierarchy,
how about re-using the existing PARENT information?
Disadvantage: the previous / next ordering is hard / impossible to guess.
Actually: the two approaches could be combined:
use the explicit index tag where available,
else fall back to parent info;
Hmm. Resembles the
TreePlugin in a localised manner.
Needs more thinking --
PeterKlausner 12 Sep 2002
This plugin has been done as at our company, people began to make a lot of user guides, howtos,... things with a sequential thread, and experience showed that it was a pain to remember to put a special tag in each topic. The parent information has to be set manually per topic, for instance, in a multiple step operation.
But I agree: It should be nice to be able to "merge" (I dont know how) this information with the parent information. At first thought, one could have thought that adding a "next" and "previous" metadata field just like parent was the good solution, but it would have been too cumbersone to use in practice.
On the possible enhancement, I may add an "top/index" link separate from "up" which would then just climb up one level in the hierarchy, if using multiple levels of bulleted items in the index.
--
ColasNahaboo - 13 Sep 2002
The installation instructions probably should include a reminder to install the necessary patch (I realize the top of the page mentions this but it could easily be missed...
--
ThomasWeigert - 07 Nov 2002
How about combining this with the
TocPlugin, and using the WebOrder topic to define the order and linkage?
WebOrder includes information about nesting, and lineal ordering -- and (as I'm using it with the
TocPlugin changes made here) it fits in with how we build multi-topic documents and books. It would make the
TocPlugin information useful for navigation as well as document printing.
--
CarlMikkelsen - 11 Feb 2003
I did a test in
http://twikiplugins.sourceforge.net/cgi-bin/twiki/view/Sandbox/MartinsNavbarPluginTest
- I wanted to be able to dynamically generate a list and use the output of a query to drive the index.
It does not work - the first item is the first hardcoded item, in this case WebIndex, not the first result of the search. Is there way to get it to drive from the output of a search?
--
MartinCleaver - 15 Oct 2004
checked
.zip into
CVSplugins:NavbarPlugin
--
WillNorris - 24 Nov 2004
The
NavBarPlugin does not seem to work post-Cairo (in particular, for 4.x releases). Any chance of getting a fix? I believe we are running the 1.2 release of 20 Sep 2002.
--
HarlanStenn - 09 Oct 2006
When I install the
NavBar Plugin on TWiki 4.1.2 and activate in with configure, I can not access the TWiki anymore. Attempts to view any page result in an error message:
Can't use string ("NAVBARPLUGIN_EXAMPLE") as a HASH ref while "strict refs" in use at /twiki/lib/TWiki/Prefs.pm line 246.
Any ideas?
--
MartinMayer - 07 Aug 2007
This plugin probably uses internal functions of TWiki. They need to be replaced by official plugin API functions,
TWikiFuncDotPm. A common mistake is the
TWiki::Prefs::getPreferencesValue, which should be
TWiki::Func::getPreferencesValue.
--
PeterThoeny - 12 Aug 2007