all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Filip Schauer <f.schauer@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Christoph Heiss <c.heiss@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH installer 1/1] fix #4869: Show state in management interface ComboBox
Date: Wed, 11 Oct 2023 11:54:52 +0200	[thread overview]
Message-ID: <841632e7-f011-9bb9-f29f-60761e02699d@proxmox.com> (raw)
In-Reply-To: <4e4c00c7-5412-4bec-9952-8497f609b71d@proxmox.com>

The green circle is not displayed correctly by the PVE installer as it
does not have the corresponding emoji font package. However, the
suggested circles for DOWN are rendered correctly.

Alternatively we could use an arrow pointing either ⬆ (UP) or ⬇ (DOWN).

https://unicode-explorer.com/c/2B06
https://unicode-explorer.com/c/2B07

These arrows are also displayed correctly by the PVE installer.


On 10/10/2023 15:13, Thomas Lamprecht wrote:
> Am 10/10/2023 um 14:56 schrieb Christoph Heiss:
>> On Tue, Oct 10, 2023 at 01:55:43PM +0200, Thomas Lamprecht wrote:
>>> UP   -> 🟢 https://unicode-explorer.com/c/1F7E2
>> A green circle would be problematic/non-optimal for people deuteranopia
>> (red-green color blindness). So maybe some other character/symbol
>> distinctly recognizable as "being connected, up" - but purely
>> color-coding things is not something that should be done IMO.
> but those already get filled/not-filled as hint, i.e., this isn't just
> purely color coding, that's why I explicitly used a *filled* green circle
> for UP and for DOWN an *empty* one as preferred one due to vision
> impairments like color blindness, like hinted ;-)
>
> But sure, if you have a better idea for this just say so.
> IMO the proposed one should be clear enough, as not only color (useful
> for the majority of people) but also form is distinct, and I saw such
> circles being used to indicate on/off or plugged/unplugged already in
> a few UIs (such things are not easy to search for, so sorry, no concrete
> example), but that doesn't mean there might be something better that is
> still practical for both TUI and GUI.
>
>>> DOWN -> ◯ (preferred, easier to differ for vision impaired people) or ⬤
>>>          https://unicode-explorer.com/c/25EF or https://unicode-explorer.com/c/2B24
>> Do we really need to explicitly mark non-UP interfaces? I'd think the
>> fact of it being not marked UP should provide enough context in this
>> situation.
> Yes, to give clear distinction to the UP state and make them more
> distinct to each other, also to avoid text-alignment (visual symmetry)
> problems (if the symbol prefixes the iface name, which I guesstimate
> will look better).




  reply	other threads:[~2023-10-11  9:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 10:26 [pve-devel] [PATCH installer 0/1] " Filip Schauer
2023-08-04 10:26 ` [pve-devel] [PATCH installer 1/1] " Filip Schauer
2023-10-10 11:33   ` Christoph Heiss
2023-10-10 11:55     ` Thomas Lamprecht
2023-10-10 12:56       ` Christoph Heiss
2023-10-10 13:13         ` Thomas Lamprecht
2023-10-11  9:54           ` Filip Schauer [this message]
2023-10-11 10:58             ` Thomas Lamprecht
2023-10-11 15:20               ` Filip Schauer
2023-10-12 13:04                 ` Filip Schauer

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=841632e7-f011-9bb9-f29f-60761e02699d@proxmox.com \
    --to=f.schauer@proxmox.com \
    --cc=c.heiss@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal