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

List:       kde-core-devel
Subject:    Re: style, color and font changes: now or after RC1/beta2?
From:       Waldo Bastian <bastian () kde ! org>
Date:       2002-01-29 5:27:09
[Download RAW message or body]

On Monday 28 January 2002 06:12 pm, Dirk Mueller wrote:
> On Die, 29 Jan 2002, Dirk Mueller wrote:
> > Qt only apps in the KDE desktop - just like non Qt/KDE apps as well. This
> > is one step in the right direction.
>
> Just to clarify: I don't want to migrate to QSettings or away from
> KStandarddirs. But using the Qt configuration settings and eventually
> modifying them on our own integrated in KControl is just a small step back
> compared to the gain of the common look and feel. I think it is worth doing
> it. Its just the style settings, nothing more. I do appreciate that finally
> Qt 3.x can handle that on its own, and we should let it do it.

"Not moving away from KStandardDirs" and "Letting Qt 3.x handle the style 
settings" seems mutual exclusive to me. 

I would like to be able to setup different KDEDIRS and have my KDE 
applications look based on that KDEDIRS setting. I would like to be able to 
lock down the look&feel of a desktop using the mechanisms provided for that 
in KConfig. I'm not writing all this stuff to have it sit in the dustbin 
because Qt makes poor design decisions. In case you haven't noticed, a large 
number of features in Qt appeared in KDE first. Dynamically loadable style 
modules to name a single one.

If we would have sticked with the limitations of Qt we would have 100 hundred 
different configuration files under $HOME in 100 different formats and 
messageboxes with "Retry / Fail / Abort". Sorry, but that's not how it works. 
KDE defines the policy for the KDE platform, not Qt. If Qt makes it 
impossible to implement a policy then Qt should be fixed.

Cheers,
Waldo
-- 
bastian@kde.org  |   SuSE Labs KDE Developer  |  bastian@suse.com

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