git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolai Weibull <mailing-lists.git@rawuncut.elitemail.org>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: gitk - ewww
Date: Sun, 4 Dec 2005 18:12:06 +0100	[thread overview]
Message-ID: <20051204171206.GA8819@puritan.petwork> (raw)
In-Reply-To: <Pine.LNX.4.64.0512032040240.3099@g5.osdl.org>

Linus Torvalds wrote:

> On Sun, 4 Dec 2005, Ben Clifford wrote:

> > Screen shot is at:
> > http://www/hawaga.org.uk/ben/tech/gitk-eww-1.png

> What makes _me_ go "eww" in that screenshot is that tcl/tk doesn't do
> anti-aliased fonts, but maybe that's just me, and that's apparently
> 8.5 has that fixed (at a horrible performance impact, I'm sure, but
> hey, one look at your screenshot and I'm saying "bring it on").

Just use a slightly larger font and it should be fine.  The lower-right
field, whatever that lists (changed files?) - I have never used gitk,
uses anti-aliasing, and the only problem I see is that the
commit-message listing uses a font that is way too small (or is badly
designed).  The top pane is easily readable, although it could use a
slightly larger point-size.

Anti-aliasing is only a hack for displaying text on a screen.  It's not
a substitute for choosing your fonts and point sizes with care.  A
bitmapped font designed for small point-sizes will always look more
crisp than a generic TTF at small point-sizes.

        nikolai

-- 
Nikolai Weibull: now available free of charge at http://bitwi.se/!
Born in Chicago, IL USA; currently residing in Gothenburg, Sweden.
main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}

  parent reply	other threads:[~2005-12-04 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-04  1:27 gitk - ewww Ben Clifford
2005-12-04  4:44 ` Linus Torvalds
2005-12-04  6:05   ` H. Peter Anvin
2005-12-04  9:38     ` Ben Clifford
2005-12-04  6:23   ` Junio C Hamano
2005-12-04 17:12   ` Nikolai Weibull [this message]
2005-12-06 22:54 ` Paul Mackerras

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=20051204171206.GA8819@puritan.petwork \
    --to=mailing-lists.git@rawuncut.elitemail.org \
    --cc=git@vger.kernel.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).