Re: gtk3: FileChooser schema not found

[Emmanuele Bassi <ebassi gmail com>]

Requiring the schema for settings is the fundamental tenet of the GSettings
design. By not having the schema like in GConf you are trading a bit of
convenience for less safety; a lot of bugs in GConf-using applications were
due to missing schemas or wrong fallbacks for unset keys, so when I say
"convenience" I mean for casual use and not for real applications.

A schema in GSettings is the equivalent of the UI file for GtkBuilder; in
both cases an application cannot be expected to run correctly if missing.

If you wanted unspecified storage for state, I suggest storing a file under
XDG_CONFIG_HOME; you can use GKeyFile or JSON-GLib for the serialization
format.

Ciao,
Emmanuele.

(Sorry for the quote style: I'm using my phone)

On 14 Feb 2011 23:32, "Kevin DeKorte" <kdekorte gmail com> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 02/14/2011 04:08 PM, Allin Cottrell wrote:
> On Sun, 13 Feb 2011, Allin Cottrell wrote:
>
> > I ...
To me that is probably the biggest disadvantage with using GSettings is
that the application will crash if settings can't be found. I would like
to see this behavior changed to be more like gconf where missing keys
are allowed to be missing.

Kevin



- --
Get my public GnuPG key from
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk1Zu4AACgkQ6w2kMH0L1dFfIgCfQaqAUGVbX8VAlNT4Lx8CJE7n
CeIAnissRATzC4984x82ggrxVTX2enHM
=NhdA
-----END PGP SIGNATURE-----

_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list g