Edgewall Software

Changes between Version 29 and Version 30 of TracLinks


Ignore:
Timestamp:
Aug 28, 2006, 3:23:53 PM (18 years ago)
Author:
Christopher Lenz
Comment:

Minor corrections

Legend:

Unmodified
Added
Removed
Modified

  • TracLinks

    v29 v30  
    11= Trac Links =
    2 As you might have guessed, TracLinks are a very fundamental feature of Trac.
    3 
    4 They allow hyperlinking between Trac entities (tickets, reports, changesets, Wiki
    5 pages, milestones and source files) from anywhere WikiFormatting is used.
     2TracLinks are a fundamental feature of Trac, because they allow easy hyperlinking between the various entities in the system—such as tickets, reports, changesets, Wiki pages, milestones, and source files—from anywhere WikiFormatting is used.
    63
    74TracLinks are generally of the form '''type:id''' (where ''id'' represents the
    … …  
    3835'''Note:''' The wiki:CamelCase form is rarely used, but it can be convenient to refer to
    3936pages whose names do not follow WikiPageNames rules, i.e., single words,
    40 non-alphabetic characters, etc. See WikiPageNames for more about features specific to Wiki page names Trac links.
     37non-alphabetic characters, etc. See WikiPageNames for more about features specific
     38to links to Wiki page names.
    4139
    4240Trac links using the full (non-shorthand) notation can also be given a custom
    … …  
    5755Display: [ticket:1]
    5856
    59 `wiki` is the default if the namespace part of a full link is omitted (''since [milestone:0.10]''):
     57`wiki` is the default if the namespace part of a full link is omitted (''since version 0.10''):
    6058
    6159{{{
    … …  
    6361}}}
    6462
    65 Display: [wiki:SandBox the sandbox]
     63Display: [SandBox the sandbox]
    6664
    67 It might seem a simple enough concept at a glance, but actually allows quite a complex network of information. In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made.
     65TracLinks are a very simple idea, but actually allow quite a complex network of information. In practice, it's very intuitive and simple to use, and we've found the "link trail" extremely helpful to better understand what's happening in a project or why a particular change was made.
     66
     67The following sections describe the individual link types in detail, as well as several notes advanced usage of links.
    6868
    6969== attachment: links ==
    … …  
    9797== Server-relative links ==
    9898
    99 It is often necessary to link to objects on your server that have no built-in
     99It is often useful to be able to link to objects on your server that have no built-in
    100100Trac linking mechanism, such as static resources, a `/register` page, etc. This
    101101can be achieved by simply using either an absolute path from the server root,
    102 or a relative link from the Trac environments base:
     102or a relative link from the URL of the current page:
    103103
    104104{{{