Need mainnav and metanav documentation

[ecarter]

The [mainnav] and [metanav] sections are not documented. We need to create a TracNavigation page documenting them. That page should also autodetermine the available navigation items to help the user in overriding them.

[ecarter]

Finding all the navigation items: trunk/trac/web/chrome.py@5898#L375

The 'View Tickets' nav item: /trunk/trac/ticket/report.py@5898#L50

[ThurnerRupert]

its not a bug, so it seems to block 0.11 unecessarily ...

[nkantrowitz]

Replying to ThurnerRupert:

its not a bug, so it seems to block 0.11 unecessarily ...

When the bug is submitted by two members of the dev team, you can safely assume they put it where it shoud be.

[cmlenz]

If this is not dev-oriented documentation, it should probably be added to TracInterfaceCustomization.

[ilias@…]

added some text to TracNavigation

[nkantrowitz]

Replying to ilias@lazaridis.com:

added some text to TracNavigation

Documentation was incorrect and removed.

[ThurnerRupert]

added cboos text from r521 in wiki:0.11/TracInterfaceCustomization?action=diff&version=4 as suggested by cmlenz resp elias. pls reopen if not yet sufficient.

should we delete TracNavigation?

[ilias@…]

Thank you.

Yes, it looks that TracNavigation is not needed anymore.

[nkantrowitz]

The TracNavigation page should be expanded to include information about other navigation issues. For example, sample code for adding a new link should be available. I agree it should also be summarized in TracInterfaceCustomization but as the information has a low churn rate, having it be slightly duplicitous seems okay to me given that it should be more useful to users.

[ilias@…]

This sounds rational.

Possibly the TracNavigation document should be used for developer level customization.

Mr. Kantrowitz, I ask you friendly to leave the CC field intact. It's not upon you to decide who get's notified about a ticket change and who not.