On Thursday 22 August 2002 18:21, Michael Pye wrote:
> On Thursday 22 August 2002 2:53 pm, Poletti Don wrote:

> Personally, I think it is difficult to work with the theme manager beca=
use
> it encompasses so much. Ideally, shouldn't the theme manager encompass
> everything in the look and feel branch, but nothing else? Obviously thi=
s is
> now difficult because of the (perfectly logical) window management
> branch...

I am working on thememanager kcms. a look-manager kcm that encompass=20
widget-style, kwin-style, desktop-background, kicker-background, colors,=20
icon-theme, and maby more.( I am not shure if the word look-manager makes=
 any=20
sense. Should I call it look-wizard?)

a feel-manager kcm that encomass, panel layout(kudos to Carsten Wolff), k=
eys,=20
window behavior, mouse behavior and some more.

also a speed-manager kcm that customizes the speed of the desktop. It=20
encompasses menu fadings, anti aliased fonts, and many more. It detects=20
hardware like cpu speed and render support.
I am also planning some more task oriented managers. All managers will be=
=20
extreamly easy to use, because they will only consist of one main widget=20
(e.g. a slider or a list box)
=20
I would like to putt the more easy, task oriented managers in the look & =
feel=20
tree and bury the feature oriented kc modules in a 'look & feel'->'advanc=
ed=20
settings' subtree.

Maby we can adjust our work a bit to avoid dublicated code.=20

BTW: I am not aware of the kcontrol cvs changes, because my SuSE8 make dr=
ops=20
out before it compiles kcontrol. I haven't found the problem yet.=20

Greetings

Christoph


> _______________________________________________
> kde-usability mailing list
> kde-usability@mail.kde.org
> http://mail.kde.org/mailman/listinfo/kde-usability

_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability