On 09/03/15 10:42, Johannes Meixner wrote:
Hello,
On Mar 5 16:22 Ancor Gonzalez Sosa wrote (excerpt):
https://docs.google.com/drawings/d/1cVv4FY4tWRLAnMG96Cdfvw8asTNpzhFUdKn4TEq8...
If the user want to enable and start a service he needs to do both things explicitly (and the other way around).
Is this user interface meant for experienced users or also for unexperienced users?
What I am thinking about is: When an unexperienced user reads in whatever documentation that he must for example "start apache", then YaST should provide a user interface, where even an unexperienced user can find something that matches his intent to "start apache" where YaST does everything so that the "apache" thingy works. Perhaps such a functionality belongs to a YaST module to set up a web server and not to the YaST module to configure individual services? In this case the YaST module to configure individual services is not meant to be used by unexperienced users.
In any case, an inexperienced user should, in most cases, not be starting a web server or other complex service. There is no way to make an interface for highly complex processes that is simple enough for an inexperienced user without expecting too much of them or simplifying things down, which in turn angers every other user. I think this brings up a good topic: who is YaST made for? From a SUSE perspective it is not the home/inexperienced user -- Kenneth Wimer SUSE LINUX GmbH, GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409 Nürnberg, Germany Phone: +49 911 740 53-669 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org