New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UX request: colour of "padlock" icon for dom0 #3853

Open
trueriver opened this Issue Apr 24, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@trueriver

Qubes OS version:

R4.0 (and earlier)

Affected component(s):

Menus and applications that show the various VMs


Steps to reproduce the behavior:

Open the main menu, or Qubes Manager, or anywhere else where the coloured "padlock" icon indicates the "label" of the VM.

Expected behavior:

I would prefer to see dom0 represented with a different colour to the templates (preferably a colour not available to any other VM

Actual behavior:

dom0 and Templates appear similar when represented by a "padlock" icon

General notes:

This is a UX request rather than a bug

I think it would re-inforce for newcomers the fact that dom0 is fundamentally different to any other VM if it had its own colour padlock.

It is already the case that windows look different (dom0 has a light grey title bar whereas Templates have a black one by default.

My suggestion is that the padlock icon for dom0 be one of the following
a) a light grey or white padlock outlined in black
b) a solid black padlock without the gap under the hasp, and with a yellow "!" or yellow "0" instead (ergonomic tests show that yellow shows the maximum contrast with black, rather than white as you might logically expect)
c) a different shaped icon entirely (anything of the Qubes team's choice so long as it differes noticeably from the Template icons)

My suggestion is also that whatever is chosen for dom0 be something that a user cannot change. (I think this is already so, and am mentioning it for completeness)

My belief is that visual cue would make it easier for newcomers to internalise the fact that dom0 is unique.


Related issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment