Noah Kantrowitz wrote:
> On Sep 19, 2006, at 5:50 AM, Ilias Lazaridis wrote:
> > I would like to add 'backlinks' to the trac wiki, and first of all I
> > like to ask which solutions are already available (stable).
> >
> > Secondly I like to ask the users for comments on how this should work.
> >
> > I plan to implement a plugin which implements it like this:
> >
> > * every wiki page has a parent (e.g. added on top as a macro-call
> > [[Parent("Project")]], or in some other way).
> >
> > The Backlink-Navigation bar would get the entries according to the
> > parent of a wiki page, e.g.:
> >
> > Start > Project > ProjectGuide
> >
> > A benefit of this solution is the given flexibility - the hierarchy
> > (Parents) can be changed at a later point
> >
> > An option would allow to remove the parent-name from the wiki entry,
> > thus becoming a clean & compact Navigation:
> >
> > Start > Project > ProjectGuide would become...
> > Start > Project > Guide
> >
> >
> > Any thoughts and suggestions welcome.
> >
> > context: http://dev.lazaridis.com/base/ticket/2
>
> Unless you plan to offer multi-parenting, why not use the existing
> HierWiki macros available on trac-hacks? The navigation aid you are
> describing is already implemented in the showpath patch if you use a
> standard hierarchy.

http://www.trac-hacks.org/wiki/HierWikiPlugin
http://www.trac-hacks.org/wiki/TracShowPathPatch

Those depend on names like "Project/Doc/Beta/Introduction", which I
don't want to use.

Names like "Book/Chapter/Section/Subsection" provide the hierarchy in a
fixed way .

I like to provide the flexibility to _change_ the document hierarchy
with low effort. 

.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to