Here's my two cents:
#1 is interesting as it finally explains why the buttons are below the table __ The menu has the context of the app only. Buttons have the context of the selection within a table
Users are more used to #2. It would require less time to learn the general concept. The menu has the context of the app as well as selection, depending on the menu item. The buttons below the table should, at least theoretically, not be needed at more.
#3 would probably be best for power-users who want RAID, Bcache, etc. For "normal" users I think this would be suboptimal as their use-case would then require them to understand the buttons below the table in context of the selection (and little else - the menu is mainly just confusing to them).
As for removing the buttons or not, we should keep the TUI in account when making these decisions. Personally, I think #2 with no buttons below the table might be the best option.
Regards,
Ken
On 10.09.20, 14:47, "Ancor Gonzalez Sosa" wrote:
Some time ago, we decided to make several changes in the Partitioner UI.
Check this section (or the full document if you are interested enough)
for more details:
https://github.com/yast/yast-storage-ng/blob/master/doc/partitioner_ui.md#ag...
We are currently working on adding a new menu bar, but we have two
decisions to take. We would like to have some feedback from everyone in
the YaST Team and also from SUSE UX experts, so I'm sending this to both
Ken and the yast-devel list.
For those that are not that familiar with the current UI of the
Partitioner, I added some kind of appendix at the end of this mail to
refresh minds.
First question: what approach should we follow for the menu bar?
After some discussions, we have three proposals. I created three
branches in the yast-storage-ng repository so you can play with them.
For the less technical users (downloading the repo and running the demo
may not be trivial), I'm open to create videos or have a video-call to
show them in action.
Menu proposal 1
https://github.com/ancorgs/yast-storage-ng/blob/menu_minimal/README.md
Menu proposal 2
https://github.com/ancorgs/yast-storage-ng/blob/menu_classic/README.md
Menu proposal 3
https://github.com/ancorgs/yast-storage-ng/blob/menu_explicit/README.md
We have to decide on the general approach, not on every detail. Some
entries could be relocated or renamed afterwards.
If we decide to take proposal 1, then we are done. No second question.
If we take 2 or 3, which both include options that are "contextual" to
the device currently selected, we have another thing to decide...
Second question: what to do with the menu-buttons below the tables?
(check the appendix below if you don't know what are we talking about)
Option 1. Remove them as all the functionality is already in the menus.
Option 2. Keep them as they are.
Option 3. Use simple buttons with only a small set of actions.
If we choose option 3. Selecting a disk would only show "Edit" and "View
Partitions". But not the options to create/clone partition tables (the
menu bar should be used for that). Selecting a partition would show
"Edit" and "Delete", but not resizing or moving. And so on.
What's your view on the topic?
Cheers.
And now, the appendix about the current UI, only in case you need it:
We offer many actions per each device (editing, resizing, deleting,
etc.). For that we have menu-buttons right below all the Partitioner
tables (there are too many actions, they don't fit as regular buttons).
Not all the actions make sense for all kind of devices (for example, you
cannot delete a hard disk or format an LVM volume group). So every time
a new device is selected in the table, those menu-buttons change to only
offer the actions that make sense for that type of device.
In the System table that contains all the devices, there are also
additional buttons for general actions like "Rescan Devices" or
"Configure". They have never belonged there. In the tables of a
particular technology (like RAID or Volume Management) there are buttons
to add new devices of the corresponding type.
Cheers again.
--
Ancor González Sosa
YaST Team at SUSE Software Solutions
Kenneth Wimer
Head of UX/UI Design
Products and Solutions
M: +49 173 5876891
E-Mail: wimer@suse.com
