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

glib2 3.0.7-x86-mingw32 → 3.0.8-x86-mingw32

Files changed (1058) hide show

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>