Hello, On Nov 28 20:55 member greenarrow1 wrote (shortened):
Being a computer forensics tech I see multiple operating systems and one area of the Linux system I find different than others is we seem to set everything up the way a programmer or tech sees the operation and not the end user. We use terms and info that we understand which the end user does not.
I think we must carefully keep different things separated in the discussion. On the one hand a setup tool cannot work against the design of the underlying stuff in the system. I have seen much too much nice looking design ideas for setup tools which simply cannot be implemented correctly because they are against the design of the underlying stuff in the system. On the other hand a setup tool can and must use terms and info that a normal user can understand and which are still technically correct. It is often difficult to find such terms but in very most cases it is possible.
I looked at the mock ups and I would consider icons enlarging or moving to being a confusing issue to a end user.
I think the whole idea to increase the appearance of icons for used modules is broken because the underlying assumption is that a used module is more likely to be used again but I don't see that this assumption is true because some modules are likely to be used more than once but other modules are likely to be used only once and which one belongs to which class depends on the individual users habits. In http://en.opensuse.org/YaST/Development/New_Control_Center there is "distinguish between configured and not-configured modules" It seems there is again such an underlying assumption that a used module (i.e. a "configured module") is more likely not to be used again while a not-used module seems to be "waiting to be used". I don't see that this assumption is true because some modules are likely to be used more than once but other modules are likely to be used not at all. In http://en.opensuse.org/YaST/Development/New_Control_Center there is "In order to display any module on two pages, some modules need to go. ... Grouping every thing up intelligently would save a lot modules without loosing functionality. Of course this means a lot of changes to the modules itself." This means in fact that there is no Redesign of YaST Control Center but a Redesign of the whole YaST. A nice attempt to get rid of your original problem how to make a good design for the zillions of existing modules by simply introduce a much bigger new problem (which should be solved by someone else) to reduce the number of modules. I think it is the purpose of the YaST Control Center to deal with zillions of existing modules. Have in mind that YaST is open source so that whoever likes can make as many additional modules as he likes. If the YaST Control Center fails to deal with zillions of modules, the YaST Control Center itself has to be fixed but not the individual modules. When I read http://en.opensuse.org/YaST/Development/New_Control_Center I have the feeling that you think mostly in terms of "just another UI design" but I think that UI design cannot solve any real problem. In the printing system there is a similar problem: How to to deal in a print dialog with zillions of possible options and choices which vary from printer to printer? Perhaps the ideas regarding "dealing with 5,000,000 use-cases" at http://www.mmiworks.net/eng/publications/labels/openPrinting.html might help to find a design so that the YaST Control Center can better deal with zillions of modules? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org