From: Chris Shoemaker <c.shoemaker@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: Martin Langhoff <martin.langhoff@gmail.com>,
Kay Sievers <kay.sievers@vrfy.org>,
git@vger.kernel.org
Subject: Re: [PATCH gitweb] Visually indicating patch size with horizontal bars
Date: Sun, 4 Dec 2005 20:03:35 -0500 [thread overview]
Message-ID: <20051205010335.GA4073@pe.Belkin> (raw)
In-Reply-To: <20051205000442.GB22159@pasky.or.cz>
On Mon, Dec 05, 2005 at 01:04:42AM +0100, Petr Baudis wrote:
> Dear diary, on Wed, Nov 02, 2005 at 01:12:06AM CET, I got a letter
> where Chris Shoemaker <c.shoemaker@cox.net> said that...
> > On Wed, Nov 02, 2005 at 12:33:38PM +1300, Martin Langhoff wrote:
> > > On 11/2/05, Petr Baudis <pasky@suse.cz> wrote:
> > > > What about having the color indicate the number of affected files (let's
> > > > say on a blue..red scale) and the width the size of patch?
> > >
> > > I'm a /little bit/ colour blind on the red scale -- so I vote for 2
> > > bars, each half the heigth of the current bar. ;-)
> >
> > I was going to use two bars for add vs. delete, but this could work,
> > too. I'm intending on getting back to this ASAP, but for now my
> > cvsimport problems are higher priority (see other post).
>
> Is there any progress, by the way?
A little. I decided to follow Junio's suggestion of caching the
result of "git-diff-tree -r -p $commit | git-apply --numstat" in a
BerkeleyDB. (I liked the idea of reusing the cached results on the
commit page, too.) I got a script to populate the cache, then I
suspect could be easily adapting into a commit-hook. Then I started
working on the gitweb part and tried to follow another suggestion
(Kay's, I think.) to use CSS instead of (yet another) embedded .png.
This is where I got hung up: I discovered something strange (to me, at
least) about CSS/html: I'm using the <td></td> in the fifth column of
the shortlog. I tried to use an anchor tag for the added count and
one for the deleted count. Setting "display:block" and the different
background-colors works (produces stacked horizontal bars), as does
setting various widths (an essential point), but *ONLY* using "width"
in the CSS. Using width anchor attribute simply doesn't work.
Honestly, html/css is not my strong suit and neither is perl, although
the BerkeleyDB perl API seemed simple enough.
> If you didn't manage to finish it, no big deal - but it would be great
> to have at least the last version you screenshotted, since IIRC I
> couldn't find that one either, and I would like to play with it a bit.
I'm happy for anyone to take this over. Since my excursion into css
didn't really work, I'd suggest starting with the gitweb-difftreeP.cgi
version. I will send you (and anyone else who asks) that file and the
cache population script.
-chris
next prev parent reply other threads:[~2005-12-05 1:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 20:39 [PATCH gitweb] Visually indicating patch size with horizontal bars Chris Shoemaker
2005-10-27 22:02 ` Junio C Hamano
2005-10-27 23:48 ` Chris Shoemaker
2005-10-28 0:12 ` Linus Torvalds
2005-10-28 0:50 ` Chris Shoemaker
2005-10-28 1:08 ` Martin Langhoff
2005-10-28 1:13 ` H. Peter Anvin
2005-10-28 8:29 ` Andreas Ericsson
2005-10-28 9:31 ` Junio C Hamano
2005-10-28 1:16 ` Martin Langhoff
2005-10-28 2:38 ` Linus Torvalds
2005-10-28 3:52 ` Junio C Hamano
2005-10-28 16:02 ` Linus Torvalds
2005-10-28 1:56 ` Kay Sievers
2005-10-28 2:38 ` Chris Shoemaker
2005-11-01 23:30 ` Petr Baudis
2005-11-01 23:33 ` Martin Langhoff
2005-11-01 23:43 ` Petr Baudis
2005-11-02 8:08 ` Andreas Ericsson
2005-11-02 10:37 ` Johannes Schindelin
2005-11-02 12:19 ` Andreas Ericsson
2005-11-02 12:43 ` Johannes Schindelin
2005-11-02 0:12 ` Chris Shoemaker
2005-11-02 0:26 ` Kay Sievers
2005-12-05 0:04 ` Petr Baudis
2005-12-05 1:03 ` Chris Shoemaker [this message]
2005-10-28 9:16 ` Josef Weidendorfer
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=20051205010335.GA4073@pe.Belkin \
--to=c.shoemaker@cox.net \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.org \
--cc=martin.langhoff@gmail.com \
--cc=pasky@suse.cz \
/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).