Re: GNOME CVS: gtk+ matthiasc
- From: George Staikos <staikos kde org>
- To: "Bastian, Waldo" <waldo bastian intel com>
- Cc: Gtk+ Developers <gtk-devel-list gnome org>, Jonathan Blandford <jrb redhat com>
- Subject: Re: GNOME CVS: gtk+ matthiasc
- Date: Wed, 25 Jan 2006 18:55:07 -0500
On Wednesday 25 January 2006 18:16, Bastian, Waldo wrote:
> >proxy settings from gconf to GTK+. Most applications use gconf
>
> directly
>
> >to save application data, as does the desktop in general. We dont want
> >to mirror the full gconf database via xsettings.
>
> I fully agree with that, yes.
I think an XSetting is a great step forward for this, but unfortunately only
solves a very narrow portion of the problem. As an ISV, I need to know that
my software will work on systems deployed today. This XSetting may not be
deployed in large scale for many months or even well over a year. For now,
it just adds another branch in the "if":
if (haveXSetting) {
useXSetting();
} else if (haveEnvironmentVariable) {
useThat();
} else if (haveKDE) {
// native code or shell out
} else if (haveGnome) {
// native code or shell out
} else { // Go for the app instead of system-level help
if (launchFireFox()) {
} else if (launchMozilla()) {
} else if (launchKonqueror()) {
} else if (launchNetscape4()) {
} else if (launchCXOfficeIE()) {
} else if (nowWereDesperateSoOpenXTermWithLynx()) {
}
}
Quite ugly. :-) Of course it's an exaggeration, but it's actually not far
from the truth of what happens in ISVware today. So, "go" XSettings! But
don't imagine that this solves the real problems we have today. It's a good
start at tomorrow...
--
George Staikos
KDE Developer http://www.kde.org/
Staikos Computing Services Inc. http://www.staikos.net/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]