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.
> Now, for the three UI elements mentioned above, I would
say it is a good thing that they are not manipulateable from the overview,
in order to avoid any accidental modifications.
yeah, making those editable should be avoided in general, and if over a action
toggle button, not the column that shows its current state.
Agreed.
My suggestion would be, and this is what I've included in this patch
series, to replace those checkboxes with Yes/No text. This is the way
how it is done in many other places of the system.
I would not be completely opposed, and it might be indeed a UX plus for some;
but it also has it's merits to have a language agnostic fixed width icon..
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.
If we want something prettier, we could replace/augment the text with some
fa-icon, e.g. a check-mark or an X - the important part is that they are
visually distinct from ExtJS's checkboxes.
Yeah, I'd have a slight preference towards icons, but using x for disabled
is far from ideal (denotes errors); checkboxes are best for that - and there's
quite some prior art of disabled checkboxes for showing the state..
You are right about the `x` symbols; that's why I've settled for `-` in my new
approach.
Note: Firewall configuration also uses a checkbox, however there it is
possible to enable/disable elements by clicking on the checkbox - so
this can stay as IMHO.
might want to move that to a action column with a explicit (but icon only)
toggle button.
I agree, a button would probably a nice for that.
Thanks!
[1] https://imgur.com/a/tsXegNF
--
- Lukas
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
