From: Petr Baudis <pasky@suse.cz>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Chris Shoemaker <c.shoemaker@cox.net>,
Kay Sievers <kay.sievers@vrfy.org>,
git@vger.kernel.org
Subject: Re: [PATCH gitweb] Visually indicating patch size with horizontal bars
Date: Wed, 2 Nov 2005 00:43:02 +0100 [thread overview]
Message-ID: <20051101234302.GD1431@pasky.or.cz> (raw)
In-Reply-To: <46a038f90511011533q177328fdrf4b0dd68f188282e@mail.gmail.com>
Dear diary, on Wed, Nov 02, 2005 at 12:33:38AM CET, I got a letter
where Martin Langhoff <martin.langhoff@gmail.com> told me that...
> 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. ;-)
That's certainly possible as well (if you make each of the bars of
different color), but for most people not equally visually obvious.
Perhaps we could have a knob at the bottom of the page, but that isn't
very satisfying a solution either... :-(
Another possibility is to make the height dynamic and in proportion with
the number of affected files. Or combine both the color and dynamic
height. I believe changing the color to red would make it appear as
black for the red-color-blind people?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-11-01 23:43 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 [this message]
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
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=20051101234302.GD1431@pasky.or.cz \
--to=pasky@suse.cz \
--cc=c.shoemaker@cox.net \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.org \
--cc=martin.langhoff@gmail.com \
/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).