From kde-core-devel  Tue Jan 29 05:48:17 2002
From: Waldo Bastian <bastian () kde ! org>
Date: Tue, 29 Jan 2002 05:48:17 +0000
To: kde-core-devel
Subject: Re: style, color and font changes: now or after RC1/beta2?
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=101228346305444

On Monday 28 January 2002 04:30 pm, Aaron J. Seigo wrote:
> > If Qt applications have no means of adjusting to the KDE settings the=
n
> > that is a shortcoming of Qt that should be fixed in Qt. Degrading KDE=
 to
> > overcome that is not the way to go.
>
> well, Qt _is_ the underlying toolkit here ...

Yes, so?=20

> the question is whether or not the KDE apps decide to set their own val=
ues
> despite what qt might do (which seems rediculous to me, since nothing i=
s
> gained by doing so; and only breaking look/feel consistency for qt-only
> apps is achieved). another option would be to attempt to keep the qtrc =
and
> the KDE style/color/font config entries in sync, but that is probably a
> fool's errand ...
>
> the only "fool proof" mechanism that i can see for achieving style
> consistency between qt and kde applications is by allowing QApplication=
 to
> do its thing, and modify those settings using the kde control panels (u=
sing
> KConfig)

I think we should treat Qt just as we treat GTK. Upon start we can write =
out a=20
=2Eqtrc based on the values that we read from our own config files, just =
as we=20
do with a .gtkrc.

KDE applications will continue to read their settings directly from their=
 own=20
config files, and Qt-only applications can then rely on .qtrc.

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