From: Christoph Heiss <c.heiss@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Filip Schauer <f.schauer@proxmox.com>,
Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH installer 1/1] fix #4869: Show state in management interface ComboBox
Date: Tue, 10 Oct 2023 14:56:28 +0200 [thread overview]
Message-ID: <ing2ymb3ncfzs2jy4es5af3kdaadkdwpkfbunkjaym3kwglouy@i35ivpjdn4le> (raw)
In-Reply-To: <2730c950-b0d7-45dc-af83-80ff808da9b7@proxmox.com>
On Tue, Oct 10, 2023 at 01:55:43PM +0200, Thomas Lamprecht wrote:
>
> Am 10/10/2023 um 13:33 schrieb Christoph Heiss:
> > On Fri, Aug 04, 2023 at 12:26:46PM +0200, Filip Schauer wrote:
> >> @@ -347,7 +347,7 @@ sub create_ipconf_view {
> >>
> >> my $get_device_desc = sub {
> >> my $iface = shift;
> >> - return "$iface->{name} - $iface->{mac} ($iface->{driver})";
> >> + return "$iface->{name} - $iface->{mac} ($iface->{driver}) - $iface->{state}";
> >
> > I think it would be better to only show the state if the interface is
> > actually UP - thus drawing immediate attention to these list entries and
> > not completely overloading that dropdown.
> >
> > Maybe even append it as "(UP)" instead of by dash (as it does not really
> > identify the interface, but rather is a property of it).
> >
>
> Or, if the GTK component and available fonts support it we could also use
> unicode
I like the idea!
>
> 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.
> 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.
>
> Would use less space and probably look better, if it works that is ^^
next prev parent reply other threads:[~2023-10-10 12:56 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 [this message]
2023-10-10 13:13 ` Thomas Lamprecht
2023-10-11 9:54 ` Filip Schauer
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=ing2ymb3ncfzs2jy4es5af3kdaadkdwpkfbunkjaym3kwglouy@i35ivpjdn4le \
--to=c.heiss@proxmox.com \
--cc=f.schauer@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.