| 7 | | An InterTrac link can be seen as a scoped TracLinks. |
| 8 | | It is used for referring to a Trac resource |
| 9 | | (Wiki page, changeset, ticket, ...) located in another |
| 10 | | Trac environment. |
| 11 | | |
| 12 | | == List of Active InterTrac Prefixes == |
| 13 | | |
| 14 | | [[InterTrac]] |
| 15 | | |
| 16 | | == Link Syntax == |
| 17 | | |
| 18 | | Simply use the name of the other Trac environment as a prefix, |
| 19 | | followed by a colon, ending with the resource located in the other environment. |
| | 7 | Simply use the name of the other Trac environment as a prefix, followed by a colon, ending with the resource located in the other environment: |
| 34 | | For convenience, there's also some alternative short-hand form, |
| 35 | | where one can use an alias as an immediate prefix |
| 36 | | for the identifier of a ticket, changeset or report: |
| 37 | | (e.g. `#T234`, `[T1508]`, `[trac 1508]`, ...) |
| | 21 | For convenience, there is also an alternate short-hand form, where an alias can be used as an immediate prefix for the identifier of a ticket, changeset or report, eg `#T234`, `[T1508]`, `[trac 1508]`. |
| 60 | | The `.title` information will be used for providing an useful tooltip |
| 61 | | when moving the cursor over an InterTrac links. |
| 62 | | |
| 63 | | Finally, the `.compat` option can be used to activate or disable |
| 64 | | a ''compatibility'' mode: |
| 65 | | * If the targeted Trac is running a version below [trac:milestone:0.10 0.10] |
| 66 | | ([trac:r3526 r3526] to be precise), then it doesn't know how to dispatch an InterTrac |
| 67 | | link, and it's up to the local Trac to prepare the correct link. |
| 68 | | Not all links will work that way, but the most common do. |
| 69 | | This is called the compatibility mode, and is `true` by default. |
| 70 | | * If you know that the remote Trac knows how to dispatch InterTrac links, |
| 71 | | you can explicitly disable this compatibility mode and then ''any'' |
| 72 | | TracLinks can become an InterTrac link. |
| | 40 | The `.title` information is used in a tooltip, ie when hovering the cursor over an InterTrac link. |
| 86 | | * to the log range [3300:3330]: '''(Note: the following ones need `trac.compat=false`)''' |
| 87 | | * `trac:log:@3300:3330` trac:log:@3300:3330 |
| 88 | | * `[trac 3300:3330]` [trac 3300:3330] |
| 89 | | * finally, to link to the start page of a remote trac, simply use its prefix followed by ':', inside an explicit link. Example: `[th: Trac Hacks]` (''since 0.11; note that the ''remote'' Trac has to run 0.11 for this to work'') |
| | 56 | * to the log range [3300:3330]: |
| | 57 | * `trac:log:@3300:3330` trac:log:@3300:3330 |
| | 58 | * `[trac 3300:3330]` [trac 3300:3330] |
| | 59 | * finally, to link to the start page of a remote trac, simply use its prefix followed by ':', inside an explicit link. Example: `[th: Trac Hacks]` (note that the ''remote'' Trac has to run Trac >= 0.11 for this to work'') |
| 91 | | The generic form `intertrac_prefix:module:id` is translated |
| 92 | | to the corresponding URL `<remote>/module/id`, shorthand links |
| 93 | | are specific to some modules (e.g. !#T234 is processed by the |
| 94 | | ticket module) and for the rest (`intertrac_prefix:something`), |
| 95 | | we rely on the TracSearch#quickjump facility of the remote Trac. |
| | 61 | The generic form `intertrac_prefix:module:id` is translated to the corresponding URL `<remote>/module/id`. Shorthand links are specific to some modules (e.g. !#T234 is processed by the ticket module). For the rest (`intertrac_prefix:something`), we rely on the [TracSearch#quickjump quick jump] facility of the remote Trac. |
| | 62 | |
| | 63 | == List of Active InterTrac Prefixes |
| | 64 | |
| | 65 | The following InterTrac prefixes are available on this site: |
| | 66 | |
| | 67 | [[InterTrac]] |
