Git development
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Mark Levedahl <mlevedahl@gmail.com>
Cc: Johannes Sixt via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH 5/5] gitk: avoid constructing dialog titles from text pieces
Date: Sun, 9 Aug 2026 09:27:01 +0200	[thread overview]
Message-ID: <cf2a38fe-bd22-46fb-bb1d-f994c50f0a0b@kdbg.org> (raw)
In-Reply-To: <433a3e74-c66e-40a3-9971-c8cb9692967d@gmail.com>

Am 08.08.26 um 16:55 schrieb Mark Levedahl:
> The UI
> already shows "new version" and "old version", so using new lines and old lines is consistent.

Exactly my reasoning as well!

> But, one thing missing, hinted at by your suggestion "Background of ..." is that the clear
> definition of what is being affected is poorly expressed. A complete description of each
> item would require a paragraph, probably with an example image. Trying to compress into a
> few words will always exploit context and presume some common language we expect a
> git/gitk user to understand or be able to learn in context.
> 
> Maybe some extra words and categorization would help. Consider using a longer category
> description to provide common information, for instance:
> 
>   -General Canvas Area
>                            Background
>        Marked Lines Background
>                               Main Text
>                         Selected Text
>                               Link Text
>     -Commit Differences
>                           old line text
>                         new line text
>              -old line background
>        etc.
> 
> etc, where the lines beginning with "-" are just separators and do not have an associated
> color selection button.
I am not happy with additional section titles, because they take away
vertical space. Actually, I think I'll *omit* "Diff" from the labels,
because all colors apply to the primary panel of the entire UI, which is
the diff text. Of course, the top ones listed above apply *also* to the
other panels, but let's think about that another time.

My take-aways from your proposal are:

- The entries should be rearranged. In particular, selection, marked
lines and link text must move above the diff colors.

- "old line text" and "old line background" are acceptable English
phrases. (Note: singular "line", not plural "lines".)

-- Hannes


  reply	other threads:[~2026-08-09  7:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  6:40 [PATCH 0/5] gitk: make color preferences visually more pleasing and better usable Johannes Sixt via GitGitGadget
2026-08-06  6:40 ` [PATCH 1/5] gitk: set intitial colors of swatches using the available helper Johannes Sixt via GitGitGadget
2026-08-07 14:36   ` mark
2026-08-06  6:40 ` [PATCH 2/5] gitk: condense repetitive code around color buttons into foreach loops Johannes Sixt via GitGitGadget
2026-08-07 14:37   ` mark
2026-08-06  6:40 ` [PATCH 3/5] gitk: show color preferences on the button instead of the label Johannes Sixt via GitGitGadget
2026-08-07 14:37   ` mark
2026-08-08  9:33     ` Johannes Sixt
2026-08-06  6:40 ` [PATCH 4/5] gitk: use more natural language for labels of color preferences Johannes Sixt via GitGitGadget
2026-08-06  6:40 ` [PATCH 5/5] gitk: avoid constructing dialog titles from text pieces Johannes Sixt via GitGitGadget
2026-08-07 14:37   ` mark
2026-08-08 10:00     ` Johannes Sixt
2026-08-08 14:55       ` Mark Levedahl
2026-08-09  7:27         ` Johannes Sixt [this message]
2026-08-08 16:32       ` Junio C Hamano
2026-08-09  7:04         ` Johannes Sixt

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=cf2a38fe-bd22-46fb-bb1d-f994c50f0a0b@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=mlevedahl@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