| 83 | |
| 84 | ---- |
| 85 | |
| 86 | In addition to your nice and clear analysis of the trac navigation system, I'd like to raise an issue that I do not think you address, concerning what you call "Module" and "Local" navigation. When using trac, I feel there is a lot of inconsistency here and lots of room for improvement. It seems to me that these links/actions should be further broken down into 3 categories as opposed to the 2 that you propose: |
| 87 | * '''Module Navigation Links''', for links that are useful and makes sense irrespective of whichever page we are in the module, i.e. these links do not change between module pages... for example, currently below "View Tickets" we sometimes get a "Custom Query" link, e.g. when showing a report, but not always, e.g. when displaying a ticket. But, to me it seems interesting to have the Custom Query link on every page below "View Tickets"... Furthermore, on the "Custom Query" itself, the link should not disappear, and thus be consistent with higher level navigation practices. |
| 88 | * '''Page Links''', for links that make sense exclusively for this one module page, irrespective of the current '''mode''' of the page. E.g. different views of the same page. |
| 89 | * '''Page Mode Options''', for actions that depend on the current page '''mode''', such as ''View'', ''Modify'', ... these actions are acting on this same page, and therefore should appear as appropriate. All actions should also be rendered as buttons (as active or disabled), as this implies more clearly their nature. Also, you may want in some cases to be able to display these multiple times on the same page, for convenience... such as the "Save Changes", "Cancel" options when editing a wiki page could be in 2 places, below the main textarea as well as below the previewed content. --mario |
| 90 | |
| 91 | |
| 92 | |
| 93 | |
| 94 | |
| 95 | |
| 96 | |