| 8 | | Directory entries are displayed in a list with sortable columns. The list |
| 9 | | entries can be sorted by ''name'', ''size'' or ''age'' by clicking on the column |
| 10 | | headers. The sort order can be reversed by clicking on a given column |
| 11 | | header again. |
| | 7 | At the top-level of the repository browser is the '''Repository Index''', listing all the configured repositories. |
| | 8 | Each repository has a name which is used as a path prefix in a "virtual" file hierarchy encompassing all the available repositories. |
| | 9 | One of the repositories can be configured with an empty name; this is the default repository. When such a default repository is present, its top-level files and directories are also listed, in a '''Default Repository''' section placed before the repository index. If the default repository is the only repository associated with the Trac environment, then the '''Repository Index''' will be omitted. This means that after upgrading a single-repository Trac of version 0.11 (or earlier) to a multi-repository Trac (0.12), the repository browser will look and feel the same, that single repository becoming automatically the "default" repository. |
| 13 | | The browser can be used to navigate through the directory structure |
| 14 | | by clicking on the directory names. Clicking on a file name will show |
| 15 | | the contents of the file. Clicking on the revision number of a file or |
| 16 | | directory will take you to the TracRevisionLog for that file. |
| 17 | | Note that there's also a ''Revision Log'' navigation link that will do |
| 18 | | the same for the path currently being examined. |
| | 11 | Directory entries are displayed in a list with sortable columns. The list entries can be sorted by ''Name'', ''Size'', ''Age'' or ''Author'' by clicking on the column headers. The sort order can be reversed by clicking on a given column header again. |
| 20 | | It's also possible to browse directories or files as they were in history, |
| 21 | | at any given repository revision. The default behavior is to display the |
| 22 | | latest revision but another revision number can easily be selected using |
| 23 | | the ''View revision'' input field at the top of the page. |
| | 13 | The browser can be used to navigate through the directory structure by clicking on the directory names. |
| | 14 | Clicking on a file name will show the contents of the file. |
| | 15 | Clicking on the revision number of a file or directory will take you to the TracRevisionLog for that file. |
| | 16 | Note that there's also a ''Revision Log'' navigation link that will do the same for the path currently being examined. |
| | 17 | Clicking on the ''diff'' icon after revision number will display the changes made to the files modified in that revision. |
| | 18 | Clicking on the ''Age'' of the file - will take you to that changeset in the timeline. |
| 27 | | At the top of the browser page, there's a drop-down menu which you can use |
| 28 | | to select some interesting places in the repository, for example branches or tags. |
| | 22 | The color bar next to the ''Age'' column gives a visual indication of the age of the last change to a file or directory, following the convention that '''[[span(style=color:#88f,blue)]]''' is oldest and '''[[span(style=color:#f88,red)]]''' is newest, but this can be [TracIni#browser-section configured]. |
| | 23 | |
| | 24 | At the top of the browser page, there's a ''Visit'' drop-down menu which you can use to select some interesting places in the repository, for example branches or tags. |
| 33 | | If you're using a Javascript enabled brower, you'll be able to expand and collapse folders in-place by clicking on the arrow head at the right side of a folder. Alternatively, the keyboard can also be used for this: use 'j' and 'k' to go to the next or previous entry, and 'o' (or 'Enter') to toggle between expanded and collapsed state of the selected folder or for visiting the selected file. |
| | 29 | If you're using a Javascript enabled browser, you'll be able to expand and collapse directories in-place by clicking on the arrow head at the right side of a directory. Alternatively, the [trac:TracAccessibility keyboard] can also be used for this: |
| | 30 | - use `j` and `k` to select the next or previous entry, starting with the first |
| | 31 | - `o` ('''o'''pen) to toggle between expanded and collapsed state of the selected |
| | 32 | directory or for visiting the selected file |
| | 33 | - `v` ('''v'''iew, '''v'''isit) and `<Enter>`, same as above |
| | 34 | - `r` can be used to force the '''r'''eload of an already expanded directory |
| | 35 | - `a` can be used to directly visit a file in '''a'''nnotate (blame) mode |
| | 36 | - `l` to view the '''l'''og for the selected entry |
| | 37 | If no row has been selected using `j` or `k` these keys will operate on the entry under the mouse. |
| 35 | | For the Subversion backend, some additional features are available: |
| 36 | | - support for `svn:needs-lock` property |
| 37 | | - support for `svn:externals` property (which can be [TracIni#svn:externals-section configured]) |
| | 39 | For the Subversion backend, some advanced additional features are available: |
| | 40 | - The `svn:needs-lock` property will be displayed. |
| | 41 | - Support for the `svn:mergeinfo` property showing the merged and eligible information. |
| | 42 | - Support for browsing the `svn:externals` property, which can be [TracIni#svn:externals-section configured]. |
| | 43 | - The `svn:mime-type` property is used to select the syntax highlighter for rendering the file. For example, setting `svn:mime-type` to `text/html` will ensure the file is highlighted as HTML, regardless of the file extension. It also allows selecting the character encoding used in the file content. For example, if the file content is encoded in UTF-8, set `svn:mime-type` to `text/html;charset=utf-8`. The `charset=` specification overrides the default encoding defined in the `default_charset` option of the `[trac]` section of [TracIni#trac-section trac.ini]. |
| | 44 | {{{#!comment |
| | 45 | MMM: I found this section a bit hard to understand. I changed the first item as I understood that well. |
| | 46 | but I think the other items could be changed also |
| | 47 | cboos: in the meantime, I've added the ''advanced'' word as a hint this can be a bit complex... |
| | 48 | }}} |
