GTK+ annotate plugin

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Pool wrote:

> It might also be interesting to see different colors by person, rather
> than by age.

Perhaps we could do:
hue = person and branch nick
saturation = age

That is, the newer a revision, the more intense the colour.  The older,
the less intense.

You'll note I mention "branch nick".  That's a forward-looking
statement, as they say.  I would like to include the "branch nick" as an
attribute in every revision.  By default, the "branch nick" would be the
basename of the working tree (bzr.dev for Martin, bzr.ab for me,
integration for Robert).

We would default do the branch directory basename because we don't want
to get in people's faces.  They have to pick a directory name anyhow,
and they've got their own motivations for differentiating that name from
their other branches, so it will tend to be useful.

But people could also explicitly set their branch nick to whatever they
liked.

I'm calling it a nickname because it it's descriptive, not an identity.
 Many, many people have bzr.dev directories, and some may even commit to
them.

But when you combine the person with the branch nickname, you get
something that's *almost* unique, and so would be useful for identifying
different lines of development in graphical tools.

A few nice tweaks to gannotate would be:
- - on launch, set the window width so that it doesn't scroll horizontally
- - provide an option to see a given line in the context of the file
revision where it was added.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDYjVE0F+nu1YWqI0RAgjVAJ9xs6gZdekrnzwAJ/LRZ3LA371HDACfZIlg
xIxBXRFdTXMH+L9Zx3n7PzA=
=Qx+o
-----END PGP SIGNATURE-----