[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: replacing kcontrol with system settings
From:       Olaf Schmidt <ojschmidt () kde ! org>
Date:       2007-06-17 12:45:13
Message-ID: 200706171445.14805.ojschmidt () kde ! org
[Download RAW message or body]

[ Benjamin Meyer, So., 17. Jun. 2007 ]
> It was not included in system settings for a good reason and you don't need
> to include it because one person noticed it wasn't there and brought it
> up, a handful of modules are not there

Do you have a complete list of all modules that where left out, and a 
suggestion what to do with them, and volunteers to implement those 
suggestions?

> and they were removed for good reasons.

Ellen Reitmayr, who worked with the system settings team to ensure usability, 
told me that much stuff was left out "because kcontrol is still there for the 
power users" and that she already requested to have the theme manager added 
back to system settings some time ago. She agrees with me that if kcontrol is 
removed, then we need to have a solution for all stuff in kcontrol first.

The reason I am especially concerned about the theme manager is that it is 
important for partially sighted users. If you portray this accessibility 
advise as the unimportant view of just "one person", then we can just as well 
shut down the HCI working group.

> Putting them both in kcontrol is (and was) just stupid.  It just begs
> the user question: "Which is the right way to configure my
> background?"  How would we document that action?

I agree with this usability concern, and I am not objecting to fix this 
problem. I am only objecting to fix it the GNOME way (remove all stuff that 
has usability bugs, instead of fixing the usability bugs).

Olaf
[prev in list] [next in list] [prev in thread] [next in thread]