Changes between Version 2 and Version 3 of TracBrowser


Ignore:
Timestamp:
Jul 24, 2017, 9:40:52 AM (7 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracBrowser

    v2 v3  
    1 = The Trac Repository Browser =
     1= The Trac Repository Browser
     2
    23[[TracGuideToc]]
    34
    4 The Trac repository browser can be used to browse specific revisions of directories
    5 and files stored in the repositories associated with the Trac environment.
     5The Trac repository browser can be used to browse specific revisions of directories and files stored in the repositories associated with the Trac environment.
    66
    7 ''(since 0.12)'':
    8 At the top-level of the repository browser is the '''Repository Index''',
    9 listing all the configured repositories.
    10 Each repository has a name which is used as a path prefix in a
    11 "virtual" file hierarchy encompassing all the available repositories.
    12 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
    13 are also listed, in a '''Default Repository''' section placed before the
    14 repository index. If the default repository is the only repository associated
    15 with the Trac environment the '''Repository Index''' will be omitted ^[#note-multirepos (1)]^.
     7At the top-level of the repository browser is the '''Repository Index''', listing all the configured repositories.
     8Each repository has a name which is used as a path prefix in a "virtual" file hierarchy encompassing all the available repositories.
     9One 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.
    1610
    17 Directory entries are displayed in a list with sortable columns. The list
    18 entries can be sorted by ''Name'', ''Size'', ''Age'' or ''Author'' by clicking on the column
    19 headers. The sort order can be reversed by clicking on a given column
    20 header again.
     11Directory 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.
    2112
    22 The browser can be used to navigate through the directory structure
    23 by clicking on the directory names.
     13The browser can be used to navigate through the directory structure by clicking on the directory names.
    2414Clicking on a file name will show the contents of the file.
    25 Clicking on the revision number of a file or directory will take
    26 you to the TracRevisionLog for that file.
    27 Note that there's also a ''Revision Log'' navigation link that will do the
    28 same for the path currently being examined.
    29 Clicking on the ''diff'' icon after revision number will display the changes made
    30 to the files modified in that revision.
     15Clicking on the revision number of a file or directory will take you to the TracRevisionLog for that file.
     16Note that there's also a ''Revision Log'' navigation link that will do the same for the path currently being examined.
     17Clicking on the ''diff'' icon after revision number will display the changes made to the files modified in that revision.
    3118Clicking on the ''Age'' of the file - will take you to that changeset in the timeline.
    3219
    33 It's also possible to browse directories or files as they were in history,
    34 at any given repository revision. The default behavior is to display the
    35 latest revision but another revision number can easily be selected using
    36 the ''View revision'' input field at the top of the page.
     20It'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.
    3721
    38 The color bar next to the ''Age'' column gives a visual indication of the age
    39 of 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)]]'''
    41 is newest, but this can be [TracIni#browser-section configured].
     22The 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].
    4223
    43 At the top of the browser page, there's a ''Visit'' drop-down menu which you can use
    44 to select some interesting places in the repository, for example branches or tags.
     24At 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.
    4525This is sometimes referred to as the ''browser quickjump'' facility.
    4626The precise meaning and content of this menu depends on your repository backend.
    47 For Subversion, this list contains by default the top-level trunk directory
    48 and sub-directories of the top-level branches and tags directories
    49 (`/trunk`, `/branches/*`, and `/tags/*`).  This can be [TracIni#svn-section configured]
    50 for more advanced cases.
     27For 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.
    5128
    52 If you're using a Javascript enabled browser, you'll be able to expand and
    53 collapse directories in-place by clicking on the arrow head at the right side of a
    54 directory. Alternatively, the [trac:TracKeys keyboard] can also be used for this:
     29If 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:
    5530 - use `j` and `k` to select the next or previous entry, starting with the first
    5631 - `o` ('''o'''pen) to toggle between expanded and collapsed state of the selected
    … …  
    6237If no row has been selected using `j` or `k` these keys will operate on the entry under the mouse.
    6338
    64 
    6539For the Subversion backend, some advanced additional features are available:
    66  - The `svn:needs-lock` property will be displayed
    67  - Support for the `svn:mergeinfo` property showing the merged and eligible information
    68  - Support for browsing the `svn:externals` property
    69    (which can be [TracIni#svn:externals-section configured])
    70  - The `svn:mime-type` property is used to select the syntax highlighter for rendering
    71    the file. For example, setting `svn:mime-type` to `text/html` will ensure the file is
    72    highlighted as HTML, regardless of the file extension. It also allows selecting the character
    73    encoding used in the file content. For example, if the file content is encoded in UTF-8,
    74    set `svn:mime-type` to `text/html;charset=utf-8`. The `charset=` specification overrides the
    75    default encoding defined in the `default_charset` option of the `[trac]` section
    76    of [TracIni#trac-section trac.ini].
     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].
    7744{{{#!comment
    7845MMM: I found this section a bit hard to understand. I changed the first item as I understood that well.
    … …  
    8148}}}
    8249
    83 
    8450----
    85 {{{#!div style="font-size:85%"
    86 [=#note-multirepos (1)] This means that after upgrading a single-repository Trac of version
    87 0.11 (or below) to a multi-repository Trac (0.12), the repository browser will look and feel
    88 the same, that single repository becoming automatically the "default" repository.
    89 }}}
    90 
    9151See also: TracGuide, TracChangeset, TracFineGrainedPermissions