Changes between Version 11 and Version 12 of TracBrowser


Ignore:
Timestamp:
Jan 12, 2016, 11:21:52 PM (4 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracBrowser

    v11 v12  
    1 = The Trac Repository Browser
    2 
     1= The Trac Repository Browser =
    32[[TracGuideToc]]
    43
    5 The Trac repository browser can be used to browse specific revisions of directories and files stored in the repositories associated with the Trac environment.
     4The Trac repository browser can be used to browse specific revisions of directories
     5and files stored in the repositories associated with the Trac environment.
    66
    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.
     7''(since 0.12)'':
     8At the top-level of the repository browser is the '''Repository Index''',
     9listing all the configured repositories.
     10Each repository has a name which is used as a path prefix in a
     11"virtual" file hierarchy encompassing all the available repositories.
     12One 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
     13are also listed, in a '''Default Repository''' section placed before the
     14repository index. If the default repository is the only repository associated
     15with the Trac environment the '''Repository Index''' will be omitted ^[#note-multirepos (1)]^.
    1016
    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.
     17Directory entries are displayed in a list with sortable columns. The list
     18entries can be sorted by ''Name'', ''Size'', ''Age'' or ''Author'' by clicking on the column
     19headers. The sort order can be reversed by clicking on a given column
     20header again.
    1221
    13 The browser can be used to navigate through the directory structure by clicking on the directory names.
     22The browser can be used to navigate through the directory structure
     23by clicking on the directory names.
    1424Clicking 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.
     25Clicking on the revision number of a file or directory will take
     26you to the TracRevisionLog for that file.
     27Note that there's also a ''Revision Log'' navigation link that will do the
     28same for the path currently being examined.
     29Clicking on the ''diff'' icon after revision number will display the changes made
     30to the files modified in that revision.
    1831Clicking on the ''Age'' of the file - will take you to that changeset in the timeline.
    1932
    20 It's also possible to browse directories or files as they were in history, at any given repository revision. The default behavior is to display the latest revision but another revision number can easily be selected using the ''View revision'' input field at the top of the page.
     33It's also possible to browse directories or files as they were in history,
     34at any given repository revision. The default behavior is to display the
     35latest revision but another revision number can easily be selected using
     36the ''View revision'' input field at the top of the page.
    2137
    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].
     38The color bar next to the ''Age'' column gives a visual indication of the age
     39of the last change to a file or directory, following the convention that
     40'''[[span(style=color:#88f,blue)]]''' is oldest and '''[[span(style=color:#f88,red)]]'''
     41is newest, but this can be [TracIni#browser-section configured].
    2342
    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.
     43At the top of the browser page, there's a ''Visit'' drop-down menu which you can use
     44to select some interesting places in the repository, for example branches or tags.
    2545This is sometimes referred to as the ''browser quickjump'' facility.
    2646The precise meaning and content of this menu depends on your repository backend.
    27 For Subversion, this list contains by default the top-level trunk directory and sub-directories of the top-level branches and tags directories (`/trunk`, `/branches/*`, and `/tags/*`). This can be [TracIni#svn-section configured] for more advanced cases.
     47For Subversion, this list contains by default the top-level trunk directory
     48and sub-directories of the top-level branches and tags directories
     49(`/trunk`, `/branches/*`, and `/tags/*`).  This can be [TracIni#svn-section configured]
     50for more advanced cases.
    2851
    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:TracKeys 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
     52If you're using a Javascript enabled browser, you'll be able to expand and
     53collapse directories in-place by clicking on the arrow head at the right side of a
     54directory. Alternatively, the [trac:TracKeys keyboard] can also be used for this:
     55 - use `'j'` and `'k'` to select the next or previous entry, starting with the first
     56 - `'o'` (open) to toggle between expanded and collapsed state of the selected
    3257   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.
     58 - `'v'` (view, visit) and `'<Enter>'`, same as above
     59 - `'r'` can be used to force the reload of an already expanded directory
     60 - `'A'` can be used to directly visit a file in annotate (blame) mode
     61 - `'L'` to view the log for the selected entry
     62If no row has been selected using `'j'` or `'k'` these keys will operate on the entry under the mouse.
     63
     64{{{#!comment
     65MMM: I guess that some keys are upper case and some lower to avoid conflicts with browser defined keys.
     66I find for example in Firefox and IE on windows that 'a' works as well as 'A' but 'l' does not work for 'L'.
     67 cboos: 'l' is reserved for Vim like behavior, see #7867
     68}}}
    3869
    3970For 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].
     71 - The `svn:needs-lock` property will be displayed
     72 - Support for the `svn:mergeinfo` property showing the merged and eligible information
     73 - Support for browsing the `svn:externals` property
     74   (which can be [TracIni#svn:externals-section configured])
     75 - The `svn:mime-type` property is used to select the syntax highlighter for rendering
     76   the file. For example, setting `svn:mime-type` to `text/html` will ensure the file is
     77   highlighted as HTML, regardless of the file extension. It also allows selecting the character
     78   encoding used in the file content. For example, if the file content is encoded in UTF-8,
     79   set `svn:mime-type` to `text/html;charset=utf-8`. The `charset=` specification overrides the
     80   default encoding defined in the `default_charset` option of the `[trac]` section
     81   of [TracIni#trac-section trac.ini].
    4482{{{#!comment
    4583MMM: I found this section a bit hard to understand. I changed the first item as I understood that well.
     
    4886}}}
    4987
     88
    5089----
     90{{{#!div style="font-size:85%"
     91[=#note-multirepos (1)] This means that after upgrading a single-repository Trac of version
     920.11 (or below) to a multi-repository Trac (0.12), the repository browser will look and feel
     93the same, that single repository becoming automatically the "default" repository.
     94}}}
     95
    5196See also: TracGuide, TracChangeset, TracFineGrainedPermissions