Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#12 colored annotate

open
Adam Kennedy
1
2003-08-28
2003-08-28
Khad
No

Hi great cvsmonitor!
I would like suggest about colored annotation
for example version 1.1 white, 1.2 gray, 1.3 soft
green, etc.

Discussion

  • Adam Kennedy
    Adam Kennedy
    2003-08-28

    Logged In: YES
    user_id=153576

    Interesting.

    What about 1.482?

    How do you suggest allocating colours all the way out to
    arbitrary versions, and arbitrary depths 1.55.3.63

     
  • Adam Kennedy
    Adam Kennedy
    2003-08-28

    • priority: 5 --> 1
    • assigned_to: nobody --> adamkennedy
     
  • Khad
    Khad
    2003-08-28

    Logged In: YES
    user_id=391400

    hehe, just an idea,
    maybe not assigning color to every version,
    but just change the background color if the adjacent lines
    is different version

    thanks...

     
  • Adam Kennedy
    Adam Kennedy
    2003-08-28

    Logged In: YES
    user_id=153576

    What might be MORE interesting would be to take all the
    version numbers, spread them across a "first -> last" date
    range, and map that onto a red saturation, so the oldest
    version code would be black, and the newest bright red, but
    do it by time not versions.

     
  • Logged In: YES
    user_id=200346

    There's another interesting point here... Annotate needs to work for
    arbitary versions... For instance, if I'm looking at a delta from version x.1
    to x.2, the annotate link annotates at version x.2...

    In that context, it might be intersting to see colorization only for x, x.1
    and x.2... where every version <= x is some base color...

    For instance, a file which is branched at version 1.20, with 10 revisions on
    the branch would have only two colors... the default (at 1.20) and another
    color for all revisions since... Or, considering other comments here, n
    colors based on date or last n revisions since branching...

    Now, you can consider the mainline (20 revisions) or the branch (10
    revision) without considering the whole... Once the branch is merged, it is
    included in the mainline as the 21st revision...