#5857 closed defect (fixed)
Need mainnav and metanav documentation
| Reported by: | Eli Carter | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11 |
| Component: | general | Version: | devel |
| Severity: | normal | Keywords: | documentation |
| Cc: | Noah Kantrowitz, ilias@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
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.
Attachments (0)
Change History (11)
comment:1 by , 17 years ago
| Cc: | added |
|---|---|
| Keywords: | documentation added |
| Milestone: | → 0.11 |
| Version: | → devel |
comment:2 by , 17 years ago
follow-up: 4 comment:3 by , 17 years ago
| Milestone: | 0.11 → 0.11.1 |
|---|
its not a bug, so it seems to block 0.11 unecessarily …
comment:4 by , 17 years ago
| Milestone: | 0.11.1 → 0.11 |
|---|
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.
comment:5 by , 17 years ago
If this is not dev-oriented documentation, it should probably be added to TracInterfaceCustomization.
comment:7 by , 17 years ago
Replying to ilias@lazaridis.com:
added some text to TracNavigation
Documentation was incorrect and removed.
comment:10 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
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?
comment:12 by , 17 years ago
| Cc: | removed |
|---|
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.
comment:13 by , 17 years ago
| Cc: | added |
|---|
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.
Finding all the navigation items: trunk/trac/web/chrome.py@5898#L375
The 'View Tickets' nav item: trunk/trac/ticket/report.py@5898#L50