git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Fries <david@fries.net>
To: git@vger.kernel.org
Cc: Matthijs Kooijman <matthijs@stdin.nl>
Subject: Re: [PATCH] gitk: improve dark background support
Date: Wed, 10 Nov 2010 22:59:18 -0600	[thread overview]
Message-ID: <20101111045918.GA7572@spacedout.fries.net> (raw)
In-Reply-To: <20101108131412.GE22067@login.drsnuggles.stderr.nl>

On Mon, Nov 08, 2010 at 02:14:12PM +0100, Matthijs Kooijman wrote:
> Hi David,
> 
> I've been using gitk with a gray-on-black color-scheme for a while now,
> so I've given your patch a test drive. It seems to work as expected and
> indeed makes gitk a bit more pleasant to use with a dark color scheme.
> 
> I've reviewed the code a bit and it looks ok as well (though I'm hardly
> familiar with git internals, and not at all in this area).
> 
> I did encounter one minor issue, though: If you change the foreground
> color, the current view is not updated until you restart or switch views
> (or otherwise trigger a redraw, I guess). A quick look at the code shows
> that the "setfg" function contains some code that updates all canvases
> and all contexts in $fglist with the new fg color. I guess that
> something similar should be done for these tag colors to get them
> updated right away (though perhaps that should be a second patch)?

After much work and document searching I now know more about tk/tcl
than ever before and have figured out how to make the colors
dynamically update when the preferences change.  Have a look if you
will, and if it looks good I'll post it to the maintainer for
inclusion.  I'm also posting a new patch series to the list.

branch gitk_colors
git://gitorious.org/~dfries/git/dfriess-git-mainline.git

and the more disorganized work in progress branch is gitk_colors_PreSquash



> A final note: There are still some other problems with working with
> grey-on-black color scheme. In case your interested in working on those,
> I've listed them at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568470

Anything left in that list worth going over?  In terms of the .gitk
config colors what are you using and what isn't working?

my relevant .gitk config file settings,
set mainfont {Helvetica 8}
set textfont {Courier 8}
set uifont {Helvetica 9 bold}
set uicolor grey85
set bgcolor black
set fgcolor white
set colors {green red blue magenta darkgrey brown orange}
set diffcolors {red green cyan}
set markbgcolor #404060
set selectbgcolor gray50

-- 
David Fries <david@fries.net>
http://fries.net/~david/ (PGP encryption key available)

      reply	other threads:[~2010-11-11  4:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04  0:35 [PATCH] gitk: improve dark background support David Fries
2010-11-08 13:14 ` Matthijs Kooijman
2010-11-11  4:59   ` David Fries [this message]

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=20101111045918.GA7572@spacedout.fries.net \
    --to=david@fries.net \
    --cc=git@vger.kernel.org \
    --cc=matthijs@stdin.nl \
    /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).