On 9/10/20 2:47 PM, Ancor Gonzalez Sosa wrote:
[...]
First question: what approach should we follow for the menu bar?
[...]
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.
I like them all equally. But I would go for 2 or 3 because they allow us to simplify the buttons below each table. See below. I appreciate how explicit and easily discoverable is everything with the proposal 3. But I'm a bit concerned about its scalability for the future. Option 2 is also nice. I find it less obvious, but it offers more room for future growth. Although the fact that we already have a miscellaneous menu for stuff that doesn't fit anywhere else (currently called "actions") worries me a bit. So it's a tie between 2 and 3 for me.
[...]
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.
I clearly prefer option 3 here. The current menu-buttons are overwhelming. The interface would be much more guided if we select only two or three actions that we consider to be the common ones for each device type and we present them as normal buttons. Cheers. -- 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