From kde-look  Mon Apr 02 17:26:57 2001
From: Torsten Rahn <torsten () kde ! org>
Date: Mon, 02 Apr 2001 17:26:57 +0000
To: kde-look
Subject: Re: please comment: kdm control module
X-MARC-Message: https://marc.info/?l=kde-look&m=98623243905861

On Monday 02 April 2001 19:09, Oswald Buddenhagen wrote:
> [there was no reply on core-devel, so i repost here - this should
>  be the more appropriate list, anyway ...]
>
> hi there,
>
> as i want to make everything configurable from the module (no nasty
> xdm config files any more :-)), the amount of options will become
> overwhelming.
>
> so what do you suggest?
> as we all know, nested tabs are bad style (hmm ... why? an intuitive
> hierarchy should suffice, no?). putting everything in one "tab line"
> is inacceptable, too (esp., as i'm already hardly able to find
> distinct hotkeys).
> i thought about making a whole kcontrol submenu. this would also
> emphasize the fact, that the whole kdm setup contains many duplicate
> options from other modules - but for no user. otoh, the kdesu
> stuff had to be done for every single submenu, if we find no sensible
> solution to group it (hmm - maybe, invoke a second kcontrol instance
> with only the kdm menu options enabled?).
>
> ideas? comments?

Maybe the best solution would be to solve the current problem with themes.
Once we have a theme-standard which  is able to Save/Configure
the current Settings for icon/Widget-themes/Color-/Notification-/Keyboard- , 
... -schemes you could easily prompt the user for a file containing this 
information. 
That way the user/root could change the settings for his own desktop, 
save them as a theme and point the kdm-kcontrol-module to this theme.
This solution would get rid of a lot of bloated doubled menus which only 
would help to clutter kcontrol and decrease the start-up-time ... :-)

Greetings,
Tackat





 



> best regards