[yast-devel] Discussing another usability problem in YaST
Sending this to both Ken (SUSE's UX expert) and the yast-devel ML (for public scrutiny). We have recently implemented a new feature in YaST about installing packages that are needed to inspect the storage setup of a system. But we are not satisfied with the usability, so we wanted to have some feedback about how to do things better. Here you can find a description of the problem: https://gist.github.com/ancorgs/d2565bf505834329946a998500a326c8 Feel free to comment in that gist or via mail. Thanks. -- Ancor González Sosa YaST Team at SUSE Software Solutions -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 3/3/20 5:04 PM, Ancor Gonzalez Sosa wrote:
Sending this to both Ken (SUSE's UX expert) and the yast-devel ML (for public scrutiny).
We have recently implemented a new feature in YaST about installing packages that are needed to inspect the storage setup of a system. But we are not satisfied with the usability, so we wanted to have some feedback about how to do things better.
Here you can find a description of the problem: https://gist.github.com/ancorgs/d2565bf505834329946a998500a326c8
Feel free to comment in that gist or via mail.
My own 2 cents. I would change the dialog to something like this: ===================================== Probing LUKS failed The following package needs to be installed to fully analyze the storage devices on the system: cryptsetup If you continue without installing it, the system information presented by YaST will be incomplete. [Install] [Ignore and Continue] ======================================= In other words: - I would present the name of the package right away, with that, I don't think we need the "details" button (the exact command is not important). - Offering the possibility to abort right away is likely also not so important. The user can always abort after having closed the pop-up (all YaST modules contain a button to quit anyways). - Use a not-so-technical wording (I'm open to suggestions to improve my proposal). Good enough? More thoughts? -- Ancor González Sosa YaST Team at SUSE Software Solutions -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
V Tue, 3 Mar 2020 17:40:10 +0100
Ancor Gonzalez Sosa
On 3/3/20 5:04 PM, Ancor Gonzalez Sosa wrote:
Sending this to both Ken (SUSE's UX expert) and the yast-devel ML (for public scrutiny).
We have recently implemented a new feature in YaST about installing packages that are needed to inspect the storage setup of a system. But we are not satisfied with the usability, so we wanted to have some feedback about how to do things better.
Here you can find a description of the problem: https://gist.github.com/ancorgs/d2565bf505834329946a998500a326c8
Feel free to comment in that gist or via mail.
My own 2 cents.
I would change the dialog to something like this:
===================================== Probing LUKS failed
The following package needs to be installed to fully analyze the storage devices on the system: cryptsetup
If you continue without installing it, the system information presented by YaST will be incomplete.
[Install] [Ignore and Continue] =======================================
In other words:
- I would present the name of the package right away, with that, I don't think we need the "details" button (the exact command is not important). - Offering the possibility to abort right away is likely also not so important. The user can always abort after having closed the pop-up (all YaST modules contain a button to quit anyways). - Use a not-so-technical wording (I'm open to suggestions to improve my proposal).
Good enough? More thoughts?
Hi Ancor, In general I think it is much better your proposal just few ideas: - I keep simple Ignore or Continue, but not both - I would remove "the storage devices on" part in first sentence, so it is shorter and still correct from my POV. - If we use Ignore button, then I would change "If you continue without installing it" to "If you ignore failure" In general I would try to make it really shorter as noone reads long text, so it is better to have not 100% precise and detailed message that is short than very precise and detailed text that noone reads. BTW if you use richtext popup, then we can do some highlighting like LUKS and cryptsetup and maybe incomplete? In general highlighting keyword when user just quickly scan message. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (2)
-
Ancor Gonzalez Sosa -
Josef Reidinger