Edgewall Software

Opened 19 years ago

Closed 18 years ago

Last modified 20 months ago

#772 closed enhancement (fixed)

Automatic TOC on Wiki pages as found in DokuWiki

Reported by: Ian Leader <___ian.leader___@…> Owned by: Jonas Borgström
Priority: normal Milestone: 0.9
Component: wiki system Version: 0.7.1
Severity: normal Keywords:
Cc: trapni@… Branch:
Release Notes:
API Changes:
Internal Changes:


Ticket #771 mentions the very cool automatic TOCs in DocuWiki

Our team would find these very useful as it has become hard to find information on some of our pages as they have got rather long.

Attachments (0)

Change History (6)

comment:1 by straider, 19 years ago

Summary: Automatic TOC on Wiki pages as found in DocuWikiAutomatic TOC on Wiki pages as found in DokuWiki

IMHO, the automatic floating TOC is great, but that's just one of the best features that small PHP engine has, when compared with others. Ticket 771 was closed, and I must agree with its resolution. Nevertheless, by comparing the features between each WikiEngine, one could then pin-point the items of a Trac-FeaturesWishList with more accuracy. Please, see and update the comparision page accordingly, at http://www.splitbrain.org/dokuwiki/wiki%3Acompare.

comment:2 by ___ian.leader___@…, 18 years ago

on the subject of the resolution to ticket 771 - I agree that rst is much more powerful than a ToC floating at the top of the page - but with that power comes complexity. Most people updating our Trac Wikis (even the technical people) simply want to bash out some quick doco using the basic Wiki commands.

As people are already putting in different levels of heading, it seems that Trac is missing a trick by not having an automatic ToC - unless, of course their is a macro that we can slap at the top of the page to generate a ToC form normal heading Wiki markup (in which case we're the ones missing the trick) - that said I still think having it as an integral part of the system would be better.

comment:3 by trac-form@…, 18 years ago

The TOC macro, linked on the MacroBazaar page, does exactly what Ian proposes.

comment:4 by Christopher Lenz, 18 years ago

Component: generalwiki
Milestone: 0.9
Resolution: fixed
Status: newclosed

The [[PageOutline]] macro provides this in 0.9 (well, trunk).

You need to put the macro in manually, but that has the advantange that you don't have the box on pages where you might not want it.

comment:5 by Christian Parpart <trapni@…>, 18 years ago

Cc: trapni@… added

PageOutline seems to be already in /usr/lib/python2.3/site-packages/trac/wiki/macro.py and I've found no other place where I shall explicitely load it from, but yet, adding a

line on top of the page doesn't show any of the results…. why?

comment:6 by Christian Parpart <trapni@…>, 18 years ago

Man! Hit me! it's been on the right side of the page *g*… simply ignore my comment ;)

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Jonas Borgström to the specified user.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.