RubyGems - glib2 - Versions diffs - 3.0.7-x64-mingw32 → 3.0.8-x64-mingw32 - Mend

glib2 3.0.7-x64-mingw32 → 3.0.8-x64-mingw32

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1062) hide show

data/vendor/local/share/gtk-doc/html/gio/ch33s02.html CHANGED Viewed

@@ -2,13 +2,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Conceptual differences: GIO Reference Manual</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<title>Operations on multiple files: GIO Reference Manual</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
 <link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="ch33.html" title="Migrating from GConf to GSettings">
-<link rel="prev" href="ch33.html" title="Migrating from GConf to GSettings">
-<link rel="next" href="ch33s03.html" title="GConfClient (and GConfBridge) API conversion">
-<meta name="generator" content="GTK-Doc V1.21.1 (XML mode)">
+<link rel="up" href="ch33.html" title="Migrating from GnomeVFS to GIO">
+<link rel="prev" href="ch33.html" title="Migrating from GnomeVFS to GIO">
+<link rel="next" href="ch33s03.html" title="Mime monitoring">
+<meta name="generator" content="GTK-Doc V1.24 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -21,39 +21,20 @@
 </tr></table>
 <div class="section">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id-1.5.4.3"></a>Conceptual differences</h2></div></div></div>
+<a name="id-1.5.3.4"></a>Operations on multiple files</h2></div></div></div>
 <p>
-        Conceptually, GConf and GSettings are fairly similar. Both
-        have a concept of pluggable backends. Both keep information
-        about keys and their types in schemas. Both have a concept of
-        mandatory values, which lets you implement lock-down.
+        gnome-vfs has the dreaded <a href="/usr/share/gtk-doc/html/gnome-vfs-2.0/gnome-vfs-2.0-gnome-vfs-xfer.html#gnome-vfs-xfer-uri-list"><code class="function">gnome_vfs_xfer_uri_list()</code></a> function which
+        has tons of options and offers the equivalent of cp, mv, ln, mkdir
+        and rm at the same time.
       </p>
 <p>
-        There are some differences in the approach to schemas. GConf
-        installs the schemas into the database and has API to handle
-        schema information (<code class="function">gconf_client_get_default_from_schema()</code>,
-        <code class="function">gconf_value_get_schema()</code>, etc). GSettings on the other hand
-        assumes that an application knows its own schemas, and does
-        not provide API to handle schema information at runtime.
-        GSettings is also more strict about requiring a schema whenever
-        you want to read or write a key. To deal with more free-form
-        information that would appear in schema-less entries in GConf,
-        GSettings allows for schemas to be 'relocatable'.
-      </p>
-<p>
-        One difference in the way applications interact with their
-        settings is that with GConf you interact with a tree of
-        settings (ie the keys you pass to functions when reading
-        or writing values are actually paths with the actual name
-        of the key as the last element. With GSettings, you create
-        a GSettings object which has an implicit prefix that determines
-        where the settings get stored in the global tree of settings,
-        but the keys you pass when reading or writing values are just
-        the key names, not the full path.
+        GIO offers a much simpler I/O scheduler functionality instead, that
+        lets you schedule a function to be called in a separate thread, or
+        if threads are not available, as an idle in the mainloop.
+        See <a class="link" href="gio-GIOScheduler.html#g-io-scheduler-push-job" title="g_io_scheduler_push_job ()"><code class="function">g_io_scheduler_push_job()</code></a>.
       </p>
 </div>
 <div class="footer">
-<hr>
-          Generated by GTK-Doc V1.21.1</div>
+<hr>Generated by GTK-Doc V1.24</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gio/ch33s03.html CHANGED Viewed

@@ -2,13 +2,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>GConfClient (and GConfBridge) API conversion: GIO Reference Manual</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<title>Mime monitoring: GIO Reference Manual</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
 <link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="ch33.html" title="Migrating from GConf to GSettings">
-<link rel="prev" href="ch33s02.html" title="Conceptual differences">
-<link rel="next" href="ch33s04.html" title="Change notification">
-<meta name="generator" content="GTK-Doc V1.21.1 (XML mode)">
+<link rel="up" href="ch33.html" title="Migrating from GnomeVFS to GIO">
+<link rel="prev" href="ch33s02.html" title="Operations on multiple files">
+<link rel="next" href="ch34.html" title="Migrating from GConf to GSettings">
+<meta name="generator" content="GTK-Doc V1.24 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -17,143 +17,22 @@
 <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
 <td><a accesskey="u" href="ch33.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
 <td><a accesskey="p" href="ch33s02.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
-<td><a accesskey="n" href="ch33s04.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
+<td><a accesskey="n" href="ch34.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
 </tr></table>
 <div class="section">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id-1.5.4.4"></a>GConfClient (and GConfBridge) API conversion</h2></div></div></div>
+<a name="id-1.5.3.5"></a>Mime monitoring</h2></div></div></div>
 <p>
-        Most people use GConf via the high-level <span class="type">GConfClient</span> API.
-        The corresponding API is the <a class="link" href="GSettings.html" title="GSettings"><span class="type">GSettings</span></a> object. While not
-        every GConfClient function has a direct GSettings equivalent,
-        many do:
-        </p>
-<div class="table">
-<a name="gconf-client-vs-gsettings"></a><p class="title"><b>Table 3. </b></p>
-<div class="table-contents"><table border="1">
-<colgroup>
-<col>
-<col>
-</colgroup>
-<thead><tr>
-<th>GConfClient</th>
-<th>GSettings</th>
-</tr></thead>
-<tbody>
-<tr>
-<td><code class="function">gconf_client_get_default()</code></td>
-<td>no direct equivalent,
-                                                                   instead you call <a class="link" href="GSettings.html#g-settings-new" title="g_settings_new ()"><code class="function">g_settings_new()</code></a> for the schemas you use</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-set" title="g_settings_set ()"><code class="function">g_settings_set()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-get" title="g_settings_get ()"><code class="function">g_settings_get()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_bool()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-get-boolean" title="g_settings_get_boolean ()"><code class="function">g_settings_get_boolean()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set_bool()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-set-boolean" title="g_settings_set_boolean ()"><code class="function">g_settings_set_boolean()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_int()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-get-int" title="g_settings_get_int ()"><code class="function">g_settings_get_int()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set_int()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-set-int" title="g_settings_set_int ()"><code class="function">g_settings_set_int()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_float()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-get-double" title="g_settings_get_double ()"><code class="function">g_settings_get_double()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set_float()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-set-double" title="g_settings_set_double ()"><code class="function">g_settings_set_double()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_string()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-get-string" title="g_settings_get_string ()"><code class="function">g_settings_get_string()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set_string()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-set-string" title="g_settings_set_string ()"><code class="function">g_settings_set_string()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_list()</code></td>
-<td>for string lists, see <a class="link" href="GSettings.html#g-settings-get-strv" title="g_settings_get_strv ()"><code class="function">g_settings_get_strv()</code></a>, else see <a class="link" href="GSettings.html#g-settings-get-value" title="g_settings_get_value ()"><code class="function">g_settings_get_value()</code></a> and <a href="../glib/glib-GVariant.html#GVariant"><span class="type">GVariant</span></a> API</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_set_list()</code></td>
-<td>for string lists, see <a class="link" href="GSettings.html#g-settings-set-strv" title="g_settings_set_strv ()"><code class="function">g_settings_set_strv()</code></a>, else see <a class="link" href="GSettings.html#g-settings-set-value" title="g_settings_set_value ()"><code class="function">g_settings_set_value()</code></a> and <a href="../glib/glib-GVariant.html#GVariant"><span class="type">GVariant</span></a> API</td>
-</tr>
-<tr>
-<td><code class="function">gconf_entry_get_is_writable()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-is-writable" title="g_settings_is_writable ()"><code class="function">g_settings_is_writable()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_notify_add()</code></td>
-<td>not required, the <a class="link" href="GSettings.html#GSettings-changed" title="The “changed” signal"><span class="type">“changed”</span></a> signal is emitted automatically</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_add_dir()</code></td>
-<td>not required, each GSettings instance automatically watches all keys in its path</td>
-</tr>
-<tr>
-<td><span class="type">GConfChangeSet</span></td>
-<td>
-<a class="link" href="GSettings.html#g-settings-delay" title="g_settings_delay ()"><code class="function">g_settings_delay()</code></a>, <a class="link" href="GSettings.html#g-settings-apply" title="g_settings_apply ()"><code class="function">g_settings_apply()</code></a>
-</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_default_from_schema()</code></td>
-<td>no equivalent, applications are expected to know their schema</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_all_entries()</code></td>
-<td>no equivalent, applications are expected to know their schema, and GSettings does not allow schema-less entries</td>
-</tr>
-<tr>
-<td><code class="function">gconf_client_get_without_default()</code></td>
-<td>no equivalent</td>
-</tr>
-<tr>
-<td><code class="function">gconf_bridge_bind_property()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-bind" title="g_settings_bind ()"><code class="function">g_settings_bind()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">gconf_bridge_bind_property_full()</code></td>
-<td><a class="link" href="GSettings.html#g-settings-bind-with-mapping" title="g_settings_bind_with_mapping ()"><code class="function">g_settings_bind_with_mapping()</code></a></td>
-</tr>
-</tbody>
-</table></div>
-</div>
-<p><br class="table-break">
-      </p>
-<p>
-        GConfBridge was a third-party library that used GConf to bind an object property
-        to a particular configuration key. GSettings offers this service itself.
-      </p>
-<p>
-        There is a pattern that is sometimes used for GConf, where a setting can have
-        explicit 'value A', explicit 'value B' or 'use the system default'. With GConf,
-        'use the system default' is sometimes implemented by unsetting the user value.
-      </p>
-<p>
-        This is not possible in GSettings, since it does not have API to determine if a value
-        is the default and does not let you unset values. The recommended way (and much
-        clearer) way in which this can be implemented in GSettings is to have a separate
-        'use-system-default' boolean setting.
+        gnome-vfs offered a way to monitor the association between mime types
+        and default handlers for changes, with the <a href="/usr/share/gtk-doc/html/gnome-vfs-2.0/gnome-vfs-2.0-gnome-vfs-mime-monitor.html#GnomeVFSMIMEMonitor"><span class="type">GnomeVFSMIMEMonitor</span></a> object.
+        GIO does not offer a replacement for this functionality at this time,
+        since we have not found a compelling use case where
+        <a href="/usr/share/gtk-doc/html/gnome-vfs-2.0/gnome-vfs-2.0-gnome-vfs-mime-monitor.html#GnomeVFSMIMEMonitor"><span class="type">GnomeVFSMIMEMonitor</span></a> was used. If you think you have such a use
+        case, please report it at
+        <a class="ulink" href="http://bugzilla.gnome.org" target="_top">bugzilla.gnome.org</a>.
       </p>
 </div>
 <div class="footer">
-<hr>
-          Generated by GTK-Doc V1.21.1</div>
+<hr>Generated by GTK-Doc V1.24</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gio/ch34.html CHANGED Viewed

@@ -2,13 +2,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Migrating to GDBus: GIO Reference Manual</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<title>Migrating from GConf to GSettings: GIO Reference Manual</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
 <link rel="home" href="index.html" title="GIO Reference Manual">
 <link rel="up" href="migrating.html" title="Part III. Migrating to GIO">
-<link rel="prev" href="ch33s07.html" title="Data conversion">
-<link rel="next" href="ch34s02.html" title="API comparison">
-<meta name="generator" content="GTK-Doc V1.21.1 (XML mode)">
+<link rel="prev" href="ch33s03.html" title="Mime monitoring">
+<link rel="next" href="ch34s02.html" title="Conceptual differences">
+<meta name="generator" content="GTK-Doc V1.24 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -16,101 +16,40 @@
 <td width="100%" align="left" class="shortcuts"></td>
 <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
 <td><a accesskey="u" href="migrating.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
-<td><a accesskey="p" href="ch33s07.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
+<td><a accesskey="p" href="ch33s03.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
 <td><a accesskey="n" href="ch34s02.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
 </tr></table>
 <div class="chapter">
 <div class="titlepage"><div><div><h2 class="title">
-<a name="id-1.5.5"></a>Migrating to GDBus</h2></div></div></div>
+<a name="id-1.5.4"></a>Migrating from GConf to GSettings</h2></div></div></div>
 <div class="toc"><dl class="toc">
-<dt><span class="section"><a href="ch34.html#id-1.5.5.2">Conceptual differences</a></span></dt>
-<dt><span class="section"><a href="ch34s02.html">API comparison</a></span></dt>
-<dt><span class="section"><a href="ch34s03.html">Owning bus names</a></span></dt>
-<dt><span class="section"><a href="ch34s04.html">Creating proxies for well-known names</a></span></dt>
-<dt><span class="section"><a href="ch34s05.html">Generating code and docs</a></span></dt>
-<dd><dl>
-<dt><span class="section"><a href="ch34s05.html#gdbus-example-gdbus-codegen">Using gdbus-codegen</a></span></dt>
-<dt>
-<span class="refentrytitle"><a href="gdbus-org.gtk.GDBus.Example.ObjectManager.Animal.html">org.gtk.GDBus.Example.ObjectManager.Animal</a></span><span class="refpurpose"> — Example docs generated by gdbus-codegen</span>
-</dt>
-<dt>
-<span class="refentrytitle"><a href="gdbus-org.gtk.GDBus.Example.ObjectManager.Cat.html">org.gtk.GDBus.Example.ObjectManager.Cat</a></span><span class="refpurpose"> — More example docs generated by gdbus-codegen</span>
-</dt>
-<dt>
-<span class="refentrytitle"><a href="ExampleAnimal.html">ExampleAnimal</a></span><span class="refpurpose"> — Generated C code for the org.gtk.GDBus.Example.ObjectManager.Animal D-Bus interface</span>
-</dt>
-<dt>
-<span class="refentrytitle"><a href="ExampleCat.html">ExampleCat</a></span><span class="refpurpose"> — Generated C code for the org.gtk.GDBus.Example.ObjectManager.Cat D-Bus interface</span>
-</dt>
-<dt>
-<span class="refentrytitle"><a href="ExampleObject.html">ExampleObject</a></span><span class="refpurpose"> — Specialized GDBusObject types</span>
-</dt>
-<dt>
-<span class="refentrytitle"><a href="ExampleObjectManagerClient.html">ExampleObjectManagerClient</a></span><span class="refpurpose"> — Generated GDBusObjectManagerClient type</span>
-</dt>
-</dl></dd>
+<dt><span class="section"><a href="ch34.html#id-1.5.4.2">Before you start</a></span></dt>
+<dt><span class="section"><a href="ch34s02.html">Conceptual differences</a></span></dt>
+<dt><span class="section"><a href="ch34s03.html">GConfClient (and GConfBridge) API conversion</a></span></dt>
+<dt><span class="section"><a href="ch34s04.html">Change notification</a></span></dt>
+<dt><span class="section"><a href="ch34s05.html">Change sets</a></span></dt>
+<dt><span class="section"><a href="ch34s06.html">Schema conversion</a></span></dt>
+<dt><span class="section"><a href="ch34s07.html">Data conversion</a></span></dt>
 </dl></div>
 <div class="section">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id-1.5.5.2"></a>Conceptual differences</h2></div></div></div>
+<a name="id-1.5.4.2"></a>Before you start</h2></div></div></div>
 <p>
-      The central concepts of D-Bus are modelled in a very similar way
-      in dbus-glib and GDBus. Both have a objects representing connections,
-      proxies and method invocations. But there are some important
-      differences:
+        Converting individual applications and their settings from GConf to
+        GSettings can be done at will. But desktop-wide settings like font or
+        theme settings often have consumers in multiple modules. Therefore,
+        some consideration has to go into making sure that all users of a setting
+        are converted to GSettings at the same time or that the program
+        responsible for configuring that setting continues to update the value in
+        both places.
       </p>
-<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
-<li class="listitem"><p>
-          dbus-glib uses the <a class="ulink" href="http://www.freedesktop.org/wiki/Software/dbus#ReferenceImplementation.28dbus-daemonandlibdbus.29" target="_top">libdbus
-          reference implementation</a>, GDBus doesn't. Instead, it
-          relies on GIO streams as transport layer, and has its own
-          implementation for the the D-Bus connection setup and
-          authentication. Apart from using streams as transport,
-          avoiding libdbus also lets GDBus avoid some thorny
-          multithreading issues.
-        </p></li>
-<li class="listitem"><p>
-          dbus-glib uses the GObject type system for method arguments and
-          return values, including a homegrown container specialization
-          mechanism. GDBus relies on the <a href="../glib/glib-GVariant.html#GVariant"><span class="type">GVariant</span></a> type system which is
-          explicitly designed to match D-Bus types.
-        </p></li>
-<li class="listitem"><p>
-          dbus-glib models only D-Bus interfaces and does not provide
-          any types for objects. GDBus models both D-Bus interfaces
-          (via the <a class="link" href="GDBusInterface.html" title="GDBusInterface"><span class="type">GDBusInterface</span></a>, <a class="link" href="GDBusProxy.html" title="GDBusProxy"><span class="type">GDBusProxy</span></a> and
-          <a class="link" href="GDBusInterfaceSkeleton.html" title="GDBusInterfaceSkeleton"><span class="type">GDBusInterfaceSkeleton</span></a> types) and objects (via the
-          <a class="link" href="GDBusObject.html" title="GDBusObject"><span class="type">GDBusObject</span></a>, <a class="link" href="GDBusObjectSkeleton.html" title="GDBusObjectSkeleton"><span class="type">GDBusObjectSkeleton</span></a> and <a class="link" href="GDBusObjectProxy.html" title="GDBusObjectProxy"><span class="type">GDBusObjectProxy</span></a> types).
-        </p></li>
-<li class="listitem"><p>
-          GDBus includes native support for the <a class="ulink" href="http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties" target="_top">org.freedesktop.DBus.Properties</a> (via the <a class="link" href="GDBusProxy.html" title="GDBusProxy"><span class="type">GDBusProxy</span></a> type) and <a class="ulink" href="http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-objectmanager" target="_top">org.freedesktop.DBus.ObjectManager</a> D-Bus interfaces, dbus-glib doesn't.
-        </p></li>
-<li class="listitem"><p>
-          The typical way to export an object in dbus-glib involves
-          generating glue code from XML introspection data using
-          <span class="command"><strong>dbus-binding-tool</strong></span>. GDBus provides a
-          similar tool called <span class="command"><strong><a href="gdbus-codegen.html">gdbus-codegen</a></strong></span> that
-          can also generate Docbook D-Bus interface documentation.
-        </p></li>
-<li class="listitem"><p>
-          dbus-glib doesn't provide any convenience API for owning and
-          watching bus names, GDBus provides the <a class="link" href="gio-Owning-Bus-Names.html#g-bus-own-name" title="g_bus_own_name ()"><code class="function">g_bus_own_name()</code></a> and
-          <a class="link" href="gio-Watching-Bus-Names.html#g-bus-watch-name" title="g_bus_watch_name ()"><code class="function">g_bus_watch_name()</code></a> family of convenience functions.
-        </p></li>
-<li class="listitem"><p>
-          GDBus provides API to parse, generate and work with <a class="link" href="gio-D-Bus-Introspection-Data.html" title="D-Bus Introspection Data">Introspection
-          XML</a>, dbus-glib doesn't.
-        </p></li>
-<li class="listitem"><p>
-          GTestDBus provides API to create isolated unit tests GDBus Test Scaffolding.
-        </p></li>
-</ul></div>
 <p>
-    </p>
+        It is always a good idea to have a look at how others have handled
+        similar problems before.
+      </p>
 </div>
 </div>
 <div class="footer">
-<hr>
-          Generated by GTK-Doc V1.21.1</div>
+<hr>Generated by GTK-Doc V1.24</div>
 </body>
 </html>

data/vendor/local/share/gtk-doc/html/gio/ch34s02.html CHANGED Viewed

@@ -2,13 +2,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>API comparison: GIO Reference Manual</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<title>Conceptual differences: GIO Reference Manual</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
 <link rel="home" href="index.html" title="GIO Reference Manual">
-<link rel="up" href="ch34.html" title="Migrating to GDBus">
-<link rel="prev" href="ch34.html" title="Migrating to GDBus">
-<link rel="next" href="ch34s03.html" title="Owning bus names">
-<meta name="generator" content="GTK-Doc V1.21.1 (XML mode)">
+<link rel="up" href="ch34.html" title="Migrating from GConf to GSettings">
+<link rel="prev" href="ch34.html" title="Migrating from GConf to GSettings">
+<link rel="next" href="ch34s03.html" title="GConfClient (and GConfBridge) API conversion">
+<meta name="generator" content="GTK-Doc V1.24 (XML mode)">
 <link rel="stylesheet" href="style.css" type="text/css">
 </head>
 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
@@ -21,122 +21,38 @@
 </tr></table>
 <div class="section">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id-1.5.5.3"></a>API comparison</h2></div></div></div>
-<div class="table">
-<a name="dbus-glib-vs-gdbus"></a><p class="title"><b>Table 4. dbus-glib APIs and their GDBus counterparts</b></p>
-<div class="table-contents"><table summary="dbus-glib APIs and their GDBus counterparts" border="1">
-<colgroup>
-<col>
-<col>
-</colgroup>
-<thead><tr>
-<th>dbus-glib</th>
-<th>GDBus</th>
-</tr></thead>
-<tbody>
-<tr>
-<td><span class="type">DBusGConnection</span></td>
-<td><a class="link" href="GDBusConnection.html" title="GDBusConnection"><span class="type">GDBusConnection</span></a></td>
-</tr>
-<tr>
-<td><span class="type">DBusGProxy</span></td>
-<td>
-<a class="link" href="GDBusProxy.html" title="GDBusProxy"><span class="type">GDBusProxy</span></a>, <a class="link" href="GDBusInterface.html" title="GDBusInterface"><span class="type">GDBusInterface</span></a> - also see <a class="link" href="GDBusObjectProxy.html" title="GDBusObjectProxy"><span class="type">GDBusObjectProxy</span></a>
-</td>
-</tr>
-<tr>
-<td><span class="type">DBusGObject</span></td>
-<td>
-<a class="link" href="GDBusInterfaceSkeleton.html" title="GDBusInterfaceSkeleton"><span class="type">GDBusInterfaceSkeleton</span></a>, <a class="link" href="GDBusInterface.html" title="GDBusInterface"><span class="type">GDBusInterface</span></a> - also see <a class="link" href="GDBusObjectSkeleton.html" title="GDBusObjectSkeleton"><span class="type">GDBusObjectSkeleton</span></a>
-</td>
-</tr>
-<tr>
-<td><span class="type">DBusGMethodInvocation</span></td>
-<td><a class="link" href="GDBusMethodInvocation.html" title="GDBusMethodInvocation"><span class="type">GDBusMethodInvocation</span></a></td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_bus_get()</code></td>
-<td>
-<a class="link" href="GDBusConnection.html#g-bus-get-sync" title="g_bus_get_sync ()"><code class="function">g_bus_get_sync()</code></a>, also see
-               <a class="link" href="GDBusConnection.html#g-bus-get" title="g_bus_get ()"><code class="function">g_bus_get()</code></a>
-</td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_proxy_new_for_name()</code></td>
-<td>
-<a class="link" href="GDBusProxy.html#g-dbus-proxy-new-sync" title="g_dbus_proxy_new_sync ()"><code class="function">g_dbus_proxy_new_sync()</code></a> and
-               <a class="link" href="GDBusProxy.html#g-dbus-proxy-new-for-bus-sync" title="g_dbus_proxy_new_for_bus_sync ()"><code class="function">g_dbus_proxy_new_for_bus_sync()</code></a>, also see <a class="link" href="GDBusProxy.html#g-dbus-proxy-new" title="g_dbus_proxy_new ()"><code class="function">g_dbus_proxy_new()</code></a>
-</td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_proxy_add_signal()</code></td>
-<td>not needed, use the generic <a class="link" href="GDBusProxy.html#GDBusProxy-g-signal" title="The “g-signal” signal"><span class="type">“g-signal”</span></a>
-</td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_proxy_connect_signal()</code></td>
-<td>use <a href="../gobject/gobject-Signals.html#g-signal-connect"><code class="function">g_signal_connect()</code></a> with <a class="link" href="GDBusProxy.html#GDBusProxy-g-signal" title="The “g-signal” signal"><span class="type">“g-signal”</span></a>
-</td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_connection_register_g_object()</code></td>
-<td>
-<a class="link" href="GDBusConnection.html#g-dbus-connection-register-object" title="g_dbus_connection_register_object ()"><code class="function">g_dbus_connection_register_object()</code></a> - also see <a class="link" href="GDBusObjectManagerServer.html#g-dbus-object-manager-server-export" title="g_dbus_object_manager_server_export ()"><code class="function">g_dbus_object_manager_server_export()</code></a>
-</td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_connection_unregister_g_object()</code></td>
-<td>
-<a class="link" href="GDBusConnection.html#g-dbus-connection-unregister-object" title="g_dbus_connection_unregister_object ()"><code class="function">g_dbus_connection_unregister_object()</code></a> - also see <a class="link" href="GDBusObjectManagerServer.html#g-dbus-object-manager-server-unexport" title="g_dbus_object_manager_server_unexport ()"><code class="function">g_dbus_object_manager_server_unexport()</code></a>
-</td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_object_type_install_info()</code></td>
-<td>introspection data is installed while registering
-               an object, see <a class="link" href="GDBusConnection.html#g-dbus-connection-register-object" title="g_dbus_connection_register_object ()"><code class="function">g_dbus_connection_register_object()</code></a>
-</td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_proxy_begin_call()</code></td>
-<td><a class="link" href="GDBusProxy.html#g-dbus-proxy-call" title="g_dbus_proxy_call ()"><code class="function">g_dbus_proxy_call()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_proxy_end_call()</code></td>
-<td><a class="link" href="GDBusProxy.html#g-dbus-proxy-call-finish" title="g_dbus_proxy_call_finish ()"><code class="function">g_dbus_proxy_call_finish()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_proxy_call()</code></td>
-<td><a class="link" href="GDBusProxy.html#g-dbus-proxy-call-sync" title="g_dbus_proxy_call_sync ()"><code class="function">g_dbus_proxy_call_sync()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_error_domain_register()</code></td>
-<td><a class="link" href="gio-GDBusError.html#g-dbus-error-register-error-domain" title="g_dbus_error_register_error_domain ()"><code class="function">g_dbus_error_register_error_domain()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_error_has_name()</code></td>
-<td>no direct equivalent, see <a class="link" href="gio-GDBusError.html#g-dbus-error-get-remote-error" title="g_dbus_error_get_remote_error ()"><code class="function">g_dbus_error_get_remote_error()</code></a>
-</td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_method_return()</code></td>
-<td><a class="link" href="GDBusMethodInvocation.html#g-dbus-method-invocation-return-value" title="g_dbus_method_invocation_return_value ()"><code class="function">g_dbus_method_invocation_return_value()</code></a></td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_method_return_error()</code></td>
-<td>
-<a class="link" href="GDBusMethodInvocation.html#g-dbus-method-invocation-return-error" title="g_dbus_method_invocation_return_error ()"><code class="function">g_dbus_method_invocation_return_error()</code></a> and variants</td>
-</tr>
-<tr>
-<td><code class="function">dbus_g_method_get_sender()</code></td>
-<td><a class="link" href="GDBusMethodInvocation.html#g-dbus-method-invocation-get-sender" title="g_dbus_method_invocation_get_sender ()"><code class="function">g_dbus_method_invocation_get_sender()</code></a></td>
-</tr>
-</tbody>
-</table></div>
-</div>
-<br class="table-break">
+<a name="id-1.5.4.3"></a>Conceptual differences</h2></div></div></div>
+<p>
+        Conceptually, GConf and GSettings are fairly similar. Both
+        have a concept of pluggable backends. Both keep information
+        about keys and their types in schemas. Both have a concept of
+        mandatory values, which lets you implement lock-down.
+      </p>
+<p>
+        There are some differences in the approach to schemas. GConf
+        installs the schemas into the database and has API to handle
+        schema information (<code class="function">gconf_client_get_default_from_schema()</code>,
+        <code class="function">gconf_value_get_schema()</code>, etc). GSettings on the other hand
+        assumes that an application knows its own schemas, and does
+        not provide API to handle schema information at runtime.
+        GSettings is also more strict about requiring a schema whenever
+        you want to read or write a key. To deal with more free-form
+        information that would appear in schema-less entries in GConf,
+        GSettings allows for schemas to be 'relocatable'.
+      </p>
+<p>
+        One difference in the way applications interact with their
+        settings is that with GConf you interact with a tree of
+        settings (ie the keys you pass to functions when reading
+        or writing values are actually paths with the actual name
+        of the key as the last element. With GSettings, you create
+        a GSettings object which has an implicit prefix that determines
+        where the settings get stored in the global tree of settings,
+        but the keys you pass when reading or writing values are just
+        the key names, not the full path.
+      </p>
 </div>
 <div class="footer">
-<hr>
-          Generated by GTK-Doc V1.21.1</div>
+<hr>Generated by GTK-Doc V1.24</div>
 </body>
 </html>