KDE Control Center

Aaron J. Seigo aseigo at olympusproject.org
Sun Aug 4 22:19:01 BST 2002

Hash: SHA1

On Sunday 04 August 2002 03:03, Dominique Devriese wrote:
> "Aaron J. Seigo" <aseigo at olympusproject.org> writes:
> <snip:discussion of problems in kcontrol>
> Maybe it would help to start each kcontrol module with a clear and
> simple explanation of what it is supposed to do ?
> cheers
> domi

and then give that to a developer so they can make the module actually do that 
in a clear way so we can get rid of the explanations. ;-)

for fun: try explaining what each panel does right now as they are in CVS HEAD 
it is madenning. there are many that can't be explained simply or coherently. 
sit down with a user (aka sounding board) and explain to them out loud the 
hierarchy of the control center and what each panel does (not what it should 
do: what it does)

additionally, the name of the panel and its location within the control panel 
hierarchy needs to be enough information to guide the user since that's all 
they have to work with w/out long explorations. if we have to resort to 
multi-sentence explanations that users have to open each panel to read, we've 
completely blown it. 

besides, if we honstely expect users to read those texts, we're out of touch 
with the way most users work.

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

"Everything should be made as simple as possible, but not simpler"
    - Albert Einstein
Version: GnuPG v1.0.7 (GNU/Linux)


More information about the kde-core-devel mailing list