From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Lukas Wagner <l.wagner@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager/widget-toolkit 0/2] ui: replace non-clickable checkboxes with Yes/No text
Date: Mon, 23 Jan 2023 11:57:32 +0100 [thread overview]
Message-ID: <dc077dc9-8530-a96f-c661-b45b433e4e1e@proxmox.com> (raw)
In-Reply-To: <24dc416d-ffc6-63eb-91ea-f8a0abdd65fa@proxmox.com>
Am 23/01/2023 um 11:46 schrieb Lukas Wagner:
> On 1/20/23 15:09, Thomas Lamprecht wrote:
>>> While looking sleek, the problem with this is that from a user's
>>> perspective, a checkbox generally implies that it is operable by
>>> clicking on it (which we allow in other places, to make the matter even
>>> more confusing).
>>
>> If it's editable it gets a pointer cursor, else not.
>> I see were you're comming from, but do we also have any complaints on official
>> channels w.r.t. this?
>
> No complaints, it's just something that I've run into myself repeatedly, e.g. when
> enabling the no-subscription repo via the GUI. I think it's one of those UX
> problems that might be annoying to some users (including myself), however it's not
> severe enough that people care to report this in the bug tracker.
>
Ok, tbh. I have some faint memory that I saw some comment about this in the
distant past; IIRC it was mostly due to the the "writeable" firewall and the
"read-only" other usages using both the exact same display.
>
> I have played around a bit with FA icons, and I think I have found something that is visually
> appealing, fixed-width and where it is IMO clear that it is not an actionable UI item.
> For now, I think the nicest option is `fa-check` for enabled rows and `fa-minus` for disabled ones.
> I've created an A:B comparison [1] between the old checkboxes and the new icons.
> Please let me know what you think.
>
looks better than the status quo, especially UX-wise, and would be an option for
icon only. So, if nobody else has hard feelings (but ideally somewhat rationally
argued) for going with text over icon I'd go for your combination check-mark/minus
icon combination.
>
> [1] https://imgur.com/a/tsXegNF
>
next prev parent reply other threads:[~2023-01-23 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 11:17 Lukas Wagner
2023-01-20 11:17 ` [pve-devel] [PATCH manager 1/2] ui: backup: replication: replace non-clickable checkbox " Lukas Wagner
2023-01-20 11:17 ` [pve-devel] [PATCH widget-toolkit 2/2] repo view: " Lukas Wagner
2023-01-20 14:09 ` [pve-devel] [PATCH manager/widget-toolkit 0/2] ui: replace non-clickable checkboxes " Thomas Lamprecht
2023-01-23 10:46 ` Lukas Wagner
2023-01-23 10:57 ` Thomas Lamprecht [this message]
2023-01-23 11:01 ` Lukas Wagner
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=dc077dc9-8530-a96f-c661-b45b433e4e1e@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pve-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox