Re: [yast-devel] yast2-qt with Context Menus
On Monday 09 March 2009 14:10:43 Lukas Ocilka wrote: [...]
http://lizards.opensuse.org/2009/03/06/context-menus-in-yast-partitioner/ (menu with no compatible buttons below)
... shows the very first example of usage which is also a bit incompatible with the Thomas' statement: [...] I guess this is an example that shows the new feature and the partitioner will contain the "missing" buttons.
Thomas -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Thomas Goettlicher wrote:
On Monday 09 March 2009 14:10:43 Lukas Ocilka wrote: [...]
http://lizards.opensuse.org/2009/03/06/context-menus-in-yast-partitioner/ (menu with no compatible buttons below)
... shows the very first example of usage which is also a bit incompatible with the Thomas' statement: [...] I guess this is an example that shows the new feature and the partitioner will contain the "missing" buttons.
Hopefully :) Arvin's comment on that issue: 2009-03-06 22:29:23 That is intended so. All possible buttons (”Add Partition”, “Add RAID”, “Add Volume Group”, “Add Logical Volume”, “Add Crypt File”, “Add NFS Share”, “Edit”, “Resize”, “Delete”, “Rescan Disks”, …) would take to much space. That's why I'm for defining how should it look like if the buttons can't fit ;) L.
No nazdar,
I guess this is an example that shows the new feature and the partitioner will contain the "missing" buttons.
Hopefully :)
Arvin's comment on that issue: 2009-03-06 22:29:23 That is intended so. All possible buttons (”Add Partition”, “Add RAID”, “Add Volume Group”, “Add Logical Volume”, “Add Crypt File”, “Add NFS Share”, “Edit”, “Resize”, “Delete”, “Rescan Disks”, …) would take to much space.
That's why I'm for defining how should it look like if the buttons can't fit ;)
The "all available devices" screen of partitioner is very unfortunate example, where context menu is the only available means of accessing device type specific functions, as all above mentioned function buttons really would not fit the screen (in no resolution). In this screen, there will be only function buttons for tasks that are common for all devices and independent of the device type (e.g. Rescan Devices, Import mountpoints etc.). Moreover, there is a request to make "all available devices" non-default partitioner screen and pre-select hard disks screen instead, as partitioning the disk is far the most common task in partitioner. In all other screens there will be of course device-specific function buttons (or menu buttons) that will provide an alternative access to the funcionality from the context menu. After some time, we can consider dropping buttons under the table and rely on context menu only, but there definitely must be some transition period so that users can learn about context menus and get used to them. frozenB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Mon, Mar 09, 2009 at 03:22:03PM +0100, Katarína Machálková wrote:
No nazdar,
I guess this is an example that shows the new feature and the partitioner will contain the "missing" buttons.
Hopefully :)
Arvin's comment on that issue: 2009-03-06 22:29:23 That is intended so. All possible buttons (”Add Partition”, “Add RAID”, “Add Volume Group”, “Add Logical Volume”, “Add Crypt File”, “Add NFS Share”, “Edit”, “Resize”, “Delete”, “Rescan Disks”, …) would take to much space.
That's why I'm for defining how should it look like if the buttons can't fit ;)
The "all available devices" screen of partitioner is very unfortunate example, where context menu is the only available means of accessing device type specific functions, as all above mentioned function buttons really would not fit the screen (in no resolution). In this screen, there will be only function buttons for tasks that are common for all devices and independent of the device type (e.g. Rescan Devices, Import mountpoints etc.).
Moreover, there is a request to make "all available devices" non-default partitioner screen and pre-select hard disks screen instead, as partitioning the disk is far the most common task in partitioner.
I don't like that request: People who use LVM would want the LVM screen per default since the disk screen is mostly useless for them.
In all other screens there will be of course device-specific function buttons (or menu buttons) that will provide an alternative access to the funcionality from the context menu.
Exactly, right now the context menus are just shortcuts to ease editing. Anybody willing to compile YaST from SVN can have a look at the first implementation.
After some time, we can consider dropping buttons under the table and rely on context menu only, but there definitely must be some transition period so that users can learn about context menus and get used to them.
Another possibility might be to add a menubar and drop all "command" buttons. Users should be able to understand the concept of a menubar even if it's rarely used in YaST. And a menubar would be capable of housing 20 commands. After all the interface of the expert partitioner is not that complicated (doesn't offer so many commands) compared to user programs like Firefox, Thunderbird, Acroread or Emacs but apparently the way we design dialogs in YaST doesn't fulfil its needs. Regards, Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Dne pondělí 09 Březen 2009 18:58:32 Arvin Schnell napsal(a):
On Mon, Mar 09, 2009 at 03:22:03PM +0100, Katarína Machálková wrote:
No nazdar,
I guess this is an example that shows the new feature and the partitioner will contain the "missing" buttons.
Hopefully :)
Arvin's comment on that issue: 2009-03-06 22:29:23 That is intended so. All possible buttons (”Add Partition”, “Add RAID”, “Add Volume Group”, “Add Logical Volume”, “Add Crypt File”, “Add NFS Share”, “Edit”, “Resize”, “Delete”, “Rescan Disks”, …) would take to much space.
That's why I'm for defining how should it look like if the buttons can't fit ;)
The "all available devices" screen of partitioner is very unfortunate example, where context menu is the only available means of accessing device type specific functions, as all above mentioned function buttons really would not fit the screen (in no resolution). In this screen, there will be only function buttons for tasks that are common for all devices and independent of the device type (e.g. Rescan Devices, Import mountpoints etc.).
Moreover, there is a request to make "all available devices" non-default partitioner screen and pre-select hard disks screen instead, as partitioning the disk is far the most common task in partitioner.
I don't like that request: People who use LVM would want the LVM screen per default since the disk screen is mostly useless for them.
We can define several scenarios, for which we show different screen as default (e.g. there is a volume goroup existing). I guess there will be only a handful of them. For the others, we can stick with the disks screen. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Another possibility might be to add a menubar and drop all "command" buttons. Users should be able to understand the concept of a menubar even if it's rarely used in YaST. And a menubar would be capable of housing 20 commands.
Please do reserve menubar for global commands, applicable to all devices and/or independent of device type, just like e.g. Autoyast does it. It would be very unusual (user-unfriendly I dare to say) to modify menubar - drop/add or enable/disable its items - as the user switches between different tree branches (i.e. different device types), as not all the functions in the menu would be valid and applicable for this particular device type. B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Katarina Machalkova
Another possibility might be to add a menubar and drop all "command" buttons. Users should be able to understand the concept of a menubar even if it's rarely used in YaST. And a menubar would be capable of housing 20 commands.
Yes, I basically think the same. Never rely on a context menus only to set an option or execute a command. Context menus are often a nice shortcut but some guys do not seem to like them at all.
It would be very unusual (user-unfriendly I dare to say) to modify menubar - drop/add or enable/disable its items - as the user switches between different tree branches (i.e. different device types), as not all the functions in the menu would be valid and applicable for this particular device type.
Sure, but if something is not applicable, just make it a ghost entry. BTW, I do not agree with your statement that we should introduce such a feature peu-à-peu. Changing everything a little bit with every release is by no means user-friendly. This is often just annoying, IMHO ;-) -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (6)
-
Arvin Schnell -
Jiri Srain -
Karl Eichwalder -
Katarina Machalkova -
Lukas Ocilka -
Thomas Goettlicher