luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-27 07:56:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add a bit about autofoo for schemas

Browse Source 
Always a good idea to have copiable snipplets in a porting guide...
This commit is contained in:
Matthias Clasen 2010-04-19 08:54:01 -04:00
parent a96360ad68
commit 1064097504
1 changed files with 30 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
docs/reference/gio/migrating.xml
View File

@ -310,6 +310,36 @@ start_monitoring_trash (void)
<section> <section>
<title>Schema conversion</title> <title>Schema conversion</title>
<para>
If you are porting your application from GConf, most likely you already
have a GConf schema. GIO comes with a commandline tool
<link linkend="gsettings-schema-convert">gsettings-schema-convert</link>
that can help with the task of converting a GConf schema into
an equivalent GSettings schema. The tool is not perfect and
may need assistence in some cases.
</para>
<para>
GSettings schemas are described by XML files that need to get installed
into <filename>$datadir/glib-2.0/schemas</filename>, and need to be
compiled into a binary form by the <link linkend="gschema-compile">gschema-compile</link>
utility. GIO provides variables <literal>gsettingsschemadir</literal>
and <literal>gsettingsupdateschemacache</literal> for the location
and the command, which can be used in <filename>configure.in</filename>
as follows:
<programlisting>
AC_SUBST(gsettingsschemadir, `pkg-config --variable gsettingsschemadir gio-2.0`)
AC_SUBST(gsettingsupdateschemacache, `pkg-config --variable gsettingsupdateschemacache gio-2.0`)
</programlisting>
The corresponding <filename>Makefile.am</filename> fragment looks like
this:
<programlisting>
gsettingsschema_DATA = my.app.gschema.xml
install-data-hook:
$(gsettingsupdateschemacache) $(gsettingsschemadir)
</programlisting>
</para>
<para> <para>
One possible pitfall in doing schema conversion is that the default One possible pitfall in doing schema conversion is that the default
values in GSettings schemas are parsed by the #GVariant parser. values in GSettings schemas are parsed by the #GVariant parser.
@ -390,13 +420,6 @@ start_monitoring_trash (void)
GSettings. By the time you have finished porting your application GSettings. By the time you have finished porting your application
you must ensure that all key names are valid. you must ensure that all key names are valid.
</para> </para>
<para>
GIO comes with a commandline tool
<link linkend="gsettings-schema-convert">gsettings-schema-convert</link>
that can help with the task of converting a GConf schema into
an equivalent GSettings schema. The tool is not perfect and
may need assistence in some cases.
</para>
</section> </section>
<section><title>Data conversion</title> <section><title>Data conversion</title>