git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Waitz <tali@admingilde.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Matthijs Melchior <mmelchior@xs4all.nl>, git@vger.kernel.org
Subject: Re: Improved git-gui blame viewer
Date: Mon, 4 Jun 2007 09:38:27 +0200	[thread overview]
Message-ID: <20070604073827.GF16637@admingilde.org> (raw)
In-Reply-To: <20070604060720.GF4507@spearce.org>

[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]

hoi :)

On Mon, Jun 04, 2007 at 02:07:20AM -0400, Shawn O. Pearce wrote:
> >   When clicking on a light gray line to become a green line, then
> >   adjacent areas are not correctly colored.  A few adjacent entries
> >   become all same gray... [Look around git-gui.sh:340]
> 
> This (I think) is because of the way the color selections are
> being done.  git-gui is being stupid and just alternating colors to
> commits as they come in from `git blame --incremental`.  The thing
> about the incremental blame is I can receive data for any part of
> the file at any time.  So in general what happens is I get data for
> one part of the file, give it color A, then data for another part,
> give it color B, and then get data for part that is right next to the
> first A and assign it A again.  So you see chunks where there is no
> alternating...

If you use three colors you can always select one which is different
to the hunk above and below.  But I don't know if that would be
visually appealing...

Another nice thing would be a smooth gradient for each hunk.
Then we could use the same colors for every hunk, but the top of each
hunk would be a little bit lighter/darker than the bottom so that
it is easy to see the border.  Is that doable in Tk?
Perhaps a simple small line between hunks is enough, too?

-- 
Martin Waitz

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-04  7:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02  4:17 Improved git-gui blame viewer Shawn O. Pearce
2007-06-02 10:44 ` Matthijs Melchior
2007-06-04  6:07   ` Shawn O. Pearce
2007-06-04  7:38     ` Martin Waitz [this message]
2007-06-04  8:21       ` Shawn O. Pearce
2007-06-04  8:48         ` Martin Waitz
2007-06-04 21:26     ` Matthijs Melchior
2007-06-05  4:28       ` Shawn O. Pearce
2007-06-05 21:47         ` Matthijs Melchior
2007-06-04 16:10 ` Alex Riesen
2007-06-05  4:38   ` Shawn O. Pearce
2007-06-05 10:36     ` Alex Riesen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070604073827.GF16637@admingilde.org \
    --to=tali@admingilde.org \
    --cc=git@vger.kernel.org \
    --cc=mmelchior@xs4all.nl \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).