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 10:48:52 +0200 [thread overview]
Message-ID: <20070604084852.GG16637@admingilde.org> (raw)
In-Reply-To: <20070604082156.GI4507@spearce.org>
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
hoi :)
On Mon, Jun 04, 2007 at 04:21:56AM -0400, Shawn O. Pearce wrote:
> I think so, but its ugly. The viewer is actually 4 text widgets
> crammed next to each other. I can set the background color of a
> line by giving it a tag, so to do a gradient I have to assign a
> different background color to each line by giving each line its
> own tag (ick). Worse, in a 3 line chunk I can only do 3 colors.
> That fails your "smooth" concept. ;-)
yeah, if each line has a solid background that does not work :-(
> > Perhaps a simple small line between hunks is enough, too?
>
> That would be messy. I can certainly cause a few pixels of spacing
> to show up between chunks, but I'm reading the data "live" from the
> blame engine and putting it on screen. Adding space betwen chunks
> as I get it will cause the data to "reflow" while you are trying to
> read it. I can probably account for it with the scrollbar and adjust
> it accordingly, but at some point you will wind up seeing the text
> in the viewer pane moving around and expanding as the padding gets
> tossed in.
Well, it would work if you could just draw a one-pixel line (in some
subtle gray) inbetween lines, without changing the layout.
> BTW, I just got the jump-to-original line and restore-view-on-back
> features that Matthijs was asking about working properly. Apparently
> a call to Tk's "update" (basically just let Tk pump its event loop)
> is needed after I've finished reading the file content, but before I
> adjust the view. Its in my pu branch now (gitgui-0.7.2-58-gf9e96fd).
nice :-)
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-04 8:49 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
2007-06-04 8:21 ` Shawn O. Pearce
2007-06-04 8:48 ` Martin Waitz [this message]
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=20070604084852.GG16637@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).