On 2020-09-10 14:47, Ancor Gonzalez Sosa wrote:
Menu proposal 1 https://github.com/ancorgs/yast-storage-ng/blob/menu_minimal/README.md
This is too minimalistic for my taste. It only moves very uncommon operation to a different place.
Menu proposal 2 https://github.com/ancorgs/yast-storage-ng/blob/menu_classic/README.md
Clearly this one. I like that "Add" is now unambiguous, so it's always clear WHAT will be created. That had been a weakness in my first approach. Now it even fits for categories where several different things could be created, like in an LVM: The user can choose between adding a new volume group or adding a new logical volume. That's good. Everything else is context-sensitive, so it's absolutely clear what will happen: "Edit" and "Delete" always affect the currently selected item, "Delete All" affects all visible items. This option is the best compromise between conciseness and completeness, yet it is clear at every moment what will happen. I like this one.
Menu proposal 3 https://github.com/ancorgs/yast-storage-ng/blob/menu_explicit/README.md
This is much too overwhelming. Not only are there WAY too many toplevel menus, most of them are also completely out of place most of the time. Depending on what you selected in the tree on the left, only ONE of those technology-specific toplevel menus ("Hard Disk", "RAID", "Bcache", ...) makes sense at the same time, all others are either completely disabled at the top level (which would be very odd and very unusual), or all menu items in them would be disabled. The latter would be a UI desaster: A user would have to click through them all to discover what menu items are currently available. This completely defeats the purpose of having menus: It would make life harder for the user, not easier. Do not offer stuff that is unavailable. When I am in the "LVM" view, don't bother me with Btrfs or RAID; I'll be busy figuring out what I can do / have to do with my LVMs. Don't flood me with menu items that are all unavailable because they are irrelevant right now. Also, I miss the "Configure" menu that would lead the user to the more exotic storage technologies like iSCSI, FCoE etc.; they would probably have to be in another toplevel menu that would look even more out of place in this setup. Besides all this, consider the NCurses case. It would be a tight fit even in English even right now. And then consider languages that need more screen space like French or German. And consider that we might have to add more technologies in the future that would require new similar toplevel menus. This is clearly a killer argument all by its own, even without the usability concerns above. Kind regards -- Stefan Hundhammer <shundhammer@suse.de> YaST Developer SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org