luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-10-03 12:19:20 +02:00
Code Issues Packages Projects Releases Wiki Activity

Mention key names in the schema migration docs

Browse Source
This commit is contained in:
Matthias Clasen
2010-04-16 13:02:44 -04:00
parent 9970c6854a
commit 602625aa3d
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -273,6 +273,19 @@ start_monitoring_trash (void)
]]> ]]>
</programlisting> </programlisting>
</para> </para>
<para>
GSettings schemas have more stringent restrictions on key names
than GConf. Key names in GSettings are restricted to at most 32
characters, and must only consist of lowercase characters, numbers
and dashes, with no consecutive dashes. The first character must
not be a number or dash, and the last character cannot be '-'.
The <link linkend="gschema-compile">gschema-compile</link> schema
compiler has a <option>--allow-any-name</option> that lets you
ignore these restrictions. Note that this option is only meant
to facilitate the migration from GConf, and you should make your
key names follow the more stringent GSettings rules when you
migrate your data from GConf to dconf.
</para>
<para> <para>
GIO comes with a commandline tool GIO comes with a commandline tool
<link linkend="gsettings-schema-convert">gsettings-schema-convert</link> <link linkend="gsettings-schema-convert">gsettings-schema-convert</link>