Changes between Version 18 and Version 19 of TracProject/UiGuidelines

Timestamp:

Dec 15, 2015, 11:46:38 PM (8 years ago)

Author:

figaro

Comment:

Further cosmetic changes

TracProject/UiGuidelines

@@ -9 +9 @@
 === Current Situation
 
-''Updated to 0.10 by cboos''
-
 While the navigation interface provided by Trac 0.10 is in general clean and minimalistic, some problems of redundancy and inconsistency can be identified. The goal of this proposal is to clean-up and unify the navigation interface, and ultimately to establish guidelines for how Trac modules should hook into the navigation, so that they integrate nicely with the rest of the system.
 
@@ -19 +17 @@
  1. '''Main navigation''': Primary means for switching between modules (Wiki, Timeline, Browser, etc).
  1. '''Module navigation''': Often rendered as horizontal list of links directly beneath the main navigation bar.
- 1. '''Local navigation''': Navigational elements specific to the page currently being viewed. One example is the "Last change" in the Wiki module, another example are the "Previous/Next" links in the changeset module or ticket module.
+ 1. '''Local navigation''': Navigational elements specific to the page currently being viewed. One example is the "Last change" in the Wiki module, another example are the "Previous / Next" links in the changeset module or ticket module.
  1. '''Help links''': Links to help documents (Wiki pages, actually) relevant to the page currently being viewed.
  1. '''Alternate formats''': Links to alternate formats of the current page, such as the RSS feed for the timeline, or the comma-delimited text option for a report.
@@ -44 +42 @@
   When viewing the list of available reports, two module navigation links are available: ''Available Reports'' and ''Custom Query''. Both remain available when opening a specific report. However, when viewing the report list or the custom query, only the ''alternative'' view remains selectable.
 
-==== Conclusion
+=== Conclusion
 
 As noted in the introduction, the navigation story in Trac is inconsistent especially when it comes to differentiating between module navigation and local navigation. 
@@ -101 +99 @@
 
 ----
-One of the things I was hoping for, but haven't run across, is an easy way to edit and extend the existing navigation and page layout using Wiki pages and markup. I have been using [http://www.snipsnap.org SnipSnap] for some time, and have only recently been looking at Trac. I really like the simplicity and features integrated into Trac, but I do miss the ability to use the built-in Wiki editing to manage my page contents. For example: [http://www.snipsnap.org SnipSnap] provides 1 or more portlets, which utilize the standard wiki markup to allow a wiki to customize sidebars and other areas. If I had this capability in Trac, I could then manage and organize my wiki and the various navigation links how I see fit, without having to make changes to the *.cs files or jump through other hurdles. Would this be possible, and if so, how feasible is it with the current codebase?
+One of the things I was hoping for, but haven't run across, is an easy way to edit and extend the existing navigation and page layout using Wiki pages and markup. I have been using [http://sourceforge.net/projects/snipsnap/ SnipSnap] for some time, and have only recently been looking at Trac. I really like the simplicity and features integrated into Trac, but I do miss the ability to use the built-in Wiki editing to manage my page contents. For example, !SnipSnap provides 1 or more portlets, which utilize the standard wiki markup to allow a wiki to customize sidebars and other areas. If I had this capability in Trac, I could then manage and organize my wiki and the various navigation links how I see fit, without having to make changes to the *.cs files or jump through other hurdles. Would this be possible, and if so, how feasible is it with the current codebase?
 
 --James