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

List:       kde-usability
Subject:    kcontrol
From:       Benjamin Meyer <ben+kdeusibility () meyerhome ! net>
Date:       2004-07-26 1:54:00
Message-ID: 200407252154.07854.ben+kdeusibility () meyerhome ! net
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rather than being just another complainer person who says "KControl sucks and 
needs to be better" with nothing constructive to add, I have put together 
some things first.

Based somewhat on the already constructed changes by this mailinglist 
contained in kdebase/kcontrol/TODO I have written up first a doc specifying 
the basic grouping along with explanations of what/why.  This type of doc 
never seemed to have existed before which is part of the problem for the 
constant kcontrol changes in the past 7 years (as far back as I know)

http://www.csh.rit.edu/~benjamin/kcontrol4/kcontrol4.html

At the same time I played using QtDesigner and a little code and made a mockup 
application: 
http://www.csh.rit.edu/~benjamin/kcontrol4/screenshots/mockup.png

Then I actually sat down and fleshed it out quite a bit more to the point 
where it does actually load the kcontrol modules on your system.

http://www.csh.rit.edu/~benjamin/kcontrol4/screenshots/
http://www.csh.rit.edu/~benjamin/kcontrol4/kcontrol4.tar.bz2

You can compile it yourself and check it out.  It works just enough to play 
with the system, but probably wouldn't take much more to finish it off.

I guess the work I have done present two things:

1) A (sort of) formal doc that can be used explaining where modules go.  As 
far as I know know one has bothered to write up something like this.  Feel 
free to point me out as wrong. (no, mailing list archives don't count)

2) A different way of looking at kcontrol.  Someone said it looks like 
something from winXP, but if so that was not intensional and entirely 
accidental. 

- -Benjamin Meyer

P.S.  When seeing the modules icon's at 64x64 some of the icons really don't 
make much sense in relation with the module.

Keyboard - has a tux logo, doesn't make sense for bsd etc uses. 
User profile - uses the icon with multiple heads, it should use the icon with 
1 head.
Multiple desktops - uses the same desktop icon
Taskbar - blue K?
Colors - Why is it the mimetype colors?  Shouldn't it be the color pallette 
icon
Window Decorations - Because a plain window decoration is used in the icon the 
eye which typically ignores it will make you wonder what the icon is for.  
Maybe a really crazy window decoration should be used?  The Style icon almost 
works better than the window decoration icon for window decoration
Icons - Looks like stamps...

Anyway just a ps, if you have comments on this please reply in a separate 
e-mail than about the kcontrol topic.

- -- 
aka icefox
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBBGQ91rZ3LTw38vIRAljnAJsG0Y+hgDw63cUZFYZmfVvbvLyPiwCbBY3A
w00g07k8iRR3XB6hieI4kU8=
=UcZP
-----END PGP SIGNATURE-----
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]