On Fri, 2007-11-23 at 12:17 +0100, Thomas Goettlicher wrote:
Hi everyone,
we want to redesign the YaST Control Center. Therefore we are looking for a radical new design.
This is your chance to share your ideas regarding YaST Control Center.
Please feel free to contribute with mockups and (unconventional) ideas here: http://en.opensuse.org/YaST/Development/New_Control_Center
Thanks, Thomas
--- Hi Thomas,
Firstly, If particular hardware is not detected, the installer should not automagically (!) install neither the software for it, nor the yast modules for them. Having said that, it might be advisable of have an "shaded-out" placeholder icon, to indicate a newby-sysop that a yast-module does exist, but is not installed yet. Secondly, about the data-config: not only keep it xml, but also expand to creation for generating and validating (!!) xml-files, They are vital for cloning, auto-install, and the generation for XEN-images. Finally, most important (and difficult, if even possible): Think about a yast-yast. With this I mean a yast-module for creating.... yast-modules. Eventhough i was at the yast-workshops at Fosdem in 2006, i still think its a daunting task to create nice, practical, consistant yast-modules. A framework that pre-defines the back/cancel/next buttons with the non-graphical ALT-character code for you. If something like that exist, the community might create the nice-to-have but not-so-very-often to be used for bonding, gpg, smartcards, ssh-key-management, mysql, ser, asterisk, PAM-config or whatever. Hans -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org