Changes between Version 2 and Version 3 of TracBrowser


Ignore:
Timestamp:
May 21, 2012 12:41:39 PM (12 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracBrowser

    v2 v3  
    22[[TracGuideToc]] 
    33 
    4 The Trac repository browser can be used to browse directories  
    5 and specific revisions of files stored in the repository of the configured 
    6 version control system. 
     4The Trac repository browser can be used to browse specific revisions of directories  
     5and files stored in the repositories associated with the Trac environment. 
     6 
     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)]^. 
    716 
    817Directory 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 
     18entries can be sorted by ''Name'', ''Size'', ''Age'' or ''Author'' by clicking on the column 
    1019headers. The sort order can be reversed by clicking on a given column 
    1120header again. 
    1221 
    1322The 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. 
     23by clicking on the directory names.  
     24Clicking on a file name will show the contents of the file.  
     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. 
     31Clicking on the ''Age'' of the file - will take you to that changeset in the timeline. 
    1932 
    2033It's also possible to browse directories or files as they were in history, 
     
    2336the ''View revision'' input field at the top of the page. 
    2437 
    25 ''(since 0.11)'': 
     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]. 
    2642 
    27 The color bar next to the Age column gives a visual indication of the age 
    28 of the last change to a file or directory. In the default configuration, 
    29 blue is older and red is newer, but this can be [TracIni#browser-section configured]. 
    30  
    31 At the top of the browser page, there's a drop-down menu which you can use  
     43At the top of the browser page, there's a ''Visit'' drop-down menu which you can use  
    3244to select some interesting places in the repository, for example branches or tags.  
    3345This is sometimes referred to as the ''browser quickjump'' facility. 
    34 The precise meaning and content of this menu depends on your backend. 
    35 For Subversion, this list contains by default a few branches (`trunk` and any sub-folder of the latest `branches` top-level folder) and a few tags (any sub-folder of the latest `tags` top-level folder). This can be [TracIni#svn-section configured] for more advanced cases. 
     46The precise meaning and content of this menu depends on your repository backend. 
     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. 
    3651 
    37 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 [trac:TracKeys 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. 
     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  
     57   directory or for visiting the selected file  
     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. 
    3863 
    39 For the Subversion backend, some additional features are available: 
    40  - Support for the `svn:needs-lock` property 
    41  - Support for the `svn:externals` property (which can be [TracIni#svn:externals-section configured]) 
    42  - 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]. 
     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}}} 
     69 
     70For the Subversion backend, some advanced additional features are available: 
     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]. 
     82{{{#!comment 
     83MMM: I found this section a bit hard to understand. I changed the first item as I understood that well. 
     84but I think the other items could be changed also 
     85 cboos: in the meantime, I've added the ''advanced'' word as a hint this can be a bit complex... 
     86}}} 
     87 
    4388 
    4489---- 
     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 
    4596See also: TracGuide, TracChangeset, TracFineGrainedPermissions