Edgewall Software

Changes between Version 1 and Version 2 of InterTrac


Ignore:
Timestamp:
Apr 13, 2005, 6:04:40 PM (19 years ago)
Author:
Christian Boos
Comment:

updated to match the current implementation

Legend:

Unmodified
Added
Removed
Modified
  • InterTrac

    v1 v2  
    11= InterTrac Extension for TracLinks =
    22
    3 ''Warning: this is only a feature proposal''
     3''Warning: this is a proposal for implementing #234''
    44
    5 An InterTrac link is useful for referring from within a Trac environment
    6 to a Trac object (Wiki page, changeset, ticket, ...) located in another
    7 Trac environment, with a syntax as simple as possible.
     5== Definition ==
    86
    9 It is base on the usage of 1-letter prefix associated to
    10 a Trac environment.
     7An InterTrac link is used for referring to a Trac object
     8(Wiki page, changeset, ticket, ...) located in another
     9Trac environment.
    1110
    12 Assuming the {{{T}}} letter has been set up to refer to the
    13 Edgewall's Trac environment, one could refer to this page
    14 as {{{wiki:T:InterTrac}}}.
     11The link is composed by the target environment name, followed by a column
     12(e.g. {{{trac:}}}) follwoed by a regular TracLinks, of any flavor.
    1513
    16 TracLinks shortcuts are also adapted: #T234 refers to #234
    17 on this Trac site. [T1490] refers to the changeset 1490 on
    18 this Trac site, etc.
     14There's also an alternative short-hand form,
     15where one can use a 1, 2 or 3 letters key as an immediate
     16prefix for the identifier of a ticket, changeset or report.
     17That key is associated to an environment name in Trac's configuration file.
    1918
    20 The association between letters and Trac environments
    21 is done quite simply in an {{{[intertrac]}}} section
     19== Example ==
     20
     21Besides other local environments, which are automatically
     22detected, it is necessary to setup a configuration for the
     23InterTrac facility:
     24 * in order to refer to a remote Trac
     25 * for defining project keys
     26
     27This is done quite simply in an {{{[intertrac]}}} section
    2228within the {{{trac.ini}}} file.
    23 Currently this has to be repeated for each Trac environment,
    24 but there's work in progress concerning a
    25 [ticket:1051 centralized trac.ini], which
    26 would help greatly here.
    2729
     30Example configuration:
     31{{{
     32...
     33[intertrac]
     34trac.title = Edgewall's Trac for Trac
     35trac.url = http://projects.edgewall.com/trac
     36trac.svn = http://repos.edgewall.com/projects/trac
     37t.key = trac
     38}}}
     39
     40Now, given this configuration, one could create the following links:
     41 * to the current InterTrac page:
     42   * {{{trac:wiki:InterTrac}}}     trac:wiki:InterTrac
     43   * {{{t:wiki:InterTrac}}}        t:wiki:InterTrac
     44   * Keys are case insensitive: {{{T:wiki:InterTrac}}} → T:wiki:InterTrac
     45 * to the ticket #234:
     46   * {{{trac:ticket:234}}} trac:ticket:234
     47   * {{{trac:#234}}} trac:#234
     48   * {{{#T234}}} #T234
     49 * to the changeset [1508]:
     50   * {{{trac:changeset:1508}}} trac:changeset:1508
     51   * {{{trac:[1508]}}} trac:[1508]
     52   * {{{[T1508]}}} [T1508]
     53
     54== Notes ==
     55
     56Currently, the {{{[intertrac]}}} configuration has to be repeated
     57for each Trac environment, but there's work in progress concerning a
     58[ticket:1051 centralized trac.ini], which would help greatly here.
    2859
    2960This idea was first proposed as a patch for #234, and
    30 should be shortly proposed for inclusion in the
    31 following branch:
     61has been implemented in the following branch:
    3262source:branches/cboos-dev/intertrac-branch
    33 (i.e. source:T:branches/cboos-dev/intertrac-branch)
    3463
     64In particular, [1508] should implement all the behavior described here.