Edgewall Software

Changes between Version 15 and Version 16 of TracCrossReferences


Ignore:
Timestamp:
Aug 6, 2018, 2:43:34 PM (14 months ago)
Author:
figaro
Comment:

Typo

Legend:

Unmodified
Added
Removed
Modified
  • TracCrossReferences

    v15 v16  
    130130It should be noted that this general mechanism could be used to reimplement a few things in Trac so that they become more general:
    131131 * the ticket keywords could be reimplemented by using the `tag` relation described above. Unifying keywords and tags would enable to attach them to any Trac Object (see #695). In addition, one could fill the keyword list by picking in a list of already existing keywords.
    132  * the ticket components could be be reimplemented using a ''has-component'' relation, with the components being wiki pages [wiki:TracCrossReferences#a1 (1)]. [[comment(foot notes, anyone?)]]. The advantage would be that a ticket could have multiple components (#1730), and that the component could be documented (#1233) and used in a meaningful way in other relationships (e.g. #548, #1678 and TracMultipleProjects/SingleEnvironment#UsingComponentobjects).
     132 * the ticket components could be be reimplemented using a ''has-component'' relation, with the components being wiki pages. The advantage would be that a ticket could have multiple components (#1730), and that the component could be documented (#1233) and used in a meaningful way in other relationships (e.g. #548, #1678 and TracMultipleProjects/SingleEnvironment#UsingComponentobjects).
    133133 * idem for the versions, using a ''has-version'' relation.
    134134