Re: GSettings child schemas
- From: Osmo Antero <osmoma gmail com>
- Cc: gtk-app-devel-list gnome org
- Subject: Re: GSettings child schemas
- Date: Fri, 1 Mar 2013 11:22:45 +0000
Hello,
I will not answer to your question directly, but I have implemented
GSettings schemas for my audio-recorder app.
It may give you some tips. Please take a look at:
http://bazaar.launchpad.net/~osmoma/audio-recorder/trunk/view/head:/src/dconf.c
However, do take grated everything is correct and optimally coded ;-)
The GNOME-desktop uses normally DConf as Gsettings backend. But that's
behind the curtains.
Bom fim de semana.
Osmo Antero
On Fri, Mar 1, 2013 at 10:45 AM, Geert Janssens <info kobaltwit be> wrote:
Hi,
I'm working on replacing GConf with GSettings in the GnuCash application.
I have read through the GSettings reference documentation and migration
guide. With that I think I can mostly manage the conversion in the code.
I'm unsure about the schema conversion though. I used
gsettings-schema-convert to automatically generate GSettings compatible
schemas from the existing GConf schemas. I notice that for some schemas the
conversion tool decided to generate schemas with child schemas.
For example, after conversion I have these two schemas defined:
<schema id="org.gnucash.general" path="/aps/gnucash/general/">
<schema id="org.gnucash.general.**register" path="/apps/gnucash/general/**
register/">
(Note: I'm aware I should not use the apps for path, but this is only
temporary during the conversion.)
The second schema is marked as a child schema of the first one.
Yet due to the way our GConf schemas were organized I also have these two
schemas:
<schema id="org.gnucash.dialogs" path="/aps/gnucash/dialogs/">
<schema id="org.gnucash.dialogs.sxs" path="/apps/gnucash/dialogs/**
scheduled_trans/">
And while they also share the same path and id prefix, the second is *not*
marked as a child schema.
I found the GSettings documentation very thin on the rationale behind
child schemas and hence I have no idea about what would be best practise
here.
Should I attempt to make the schema hierarchy complete, mark schemas as
children of others wherever I can ?
Is it illegal to have two schemas of which one is in a subpath of the
other without it being a child schema ?
What benefit do I get from defining child schemas ?
Any advice here would be greatly appreciated.
Thanks,
Geert
______________________________**_________________
gtk-app-devel-list mailing list
gtk-app-devel-list gnome org
https://mail.gnome.org/**mailman/listinfo/gtk-app-**devel-list<https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list>
--
// moma
http://www.futuredesktop.org
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]