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/ch33.html CHANGED Viewed

@@ -2,13 +2,13 @@
 <html>
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Migrating from GConf to GSettings: GIO Reference Manual</title>
-<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
+<title>Migrating from GnomeVFS to GIO: 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="ch32s03.html" title="Mime monitoring">
-<link rel="next" href="ch33s02.html" title="Conceptual differences">
-<meta name="generator" content="GTK-Doc V1.21.1 (XML mode)">
+<link rel="prev" href="ch32.html" title="Migrating from POSIX to GIO">
+<link rel="next" href="ch33s02.html" title="Operations on multiple files">
+<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,41 +16,201 @@
 <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="ch32s03.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
+<td><a accesskey="p" href="ch32.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
 <td><a accesskey="n" href="ch33s02.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.4"></a>Migrating from GConf to GSettings</h2></div></div></div>
+<a name="id-1.5.3"></a>Migrating from GnomeVFS to GIO</h2></div></div></div>
 <div class="toc"><dl class="toc">
-<dt><span class="section"><a href="ch33.html#id-1.5.4.2">Before you start</a></span></dt>
-<dt><span class="section"><a href="ch33s02.html">Conceptual differences</a></span></dt>
-<dt><span class="section"><a href="ch33s03.html">GConfClient (and GConfBridge) API conversion</a></span></dt>
-<dt><span class="section"><a href="ch33s04.html">Change notification</a></span></dt>
-<dt><span class="section"><a href="ch33s05.html">Change sets</a></span></dt>
-<dt><span class="section"><a href="ch33s06.html">Schema conversion</a></span></dt>
-<dt><span class="section"><a href="ch33s07.html">Data conversion</a></span></dt>
+<dt><span class="section"><a href="ch33.html#id-1.5.3.3">Trash handling</a></span></dt>
+<dt><span class="section"><a href="ch33s02.html">Operations on multiple files</a></span></dt>
+<dt><span class="section"><a href="ch33s03.html">Mime monitoring</a></span></dt>
 </dl></div>
-<div class="section">
+<div class="table">
+<a name="gnome-vfs-vs-gio"></a><p class="title"><b>Table 2. Comparison of GnomeVFS and GIO concepts</b></p>
+<div class="table-contents"><table class="table" summary="Comparison of GnomeVFS and GIO concepts" border="1">
+<colgroup>
+<col>
+<col>
+</colgroup>
+<thead><tr>
+<th>GnomeVFS</th>
+<th>GIO</th>
+</tr></thead>
+<tbody>
+<tr>
+<td>GnomeVFSURI</td>
+<td>GFile</td>
+</tr>
+<tr>
+<td>GnomeVFSFileInfo</td>
+<td>GFileInfo</td>
+</tr>
+<tr>
+<td>GnomeVFSResult</td>
+<td>GError, with G_IO_ERROR values</td>
+</tr>
+<tr>
+<td>GnomeVFSHandle &amp; GnomeVFSAsyncHandle</td>
+<td>GInputStream or GOutputStream</td>
+</tr>
+<tr>
+<td>GnomeVFSDirectoryHandle</td>
+<td>GFileEnumerator</td>
+</tr>
+<tr>
+<td>mime type</td>
+<td>content type</td>
+</tr>
+<tr>
+<td>GnomeVFSMonitor</td>
+<td>GFileMonitor</td>
+</tr>
+<tr>
+<td>GnomeVFSVolumeMonitor</td>
+<td>GVolumeMonitor</td>
+</tr>
+<tr>
+<td>GnomeVFSVolume</td>
+<td>GMount</td>
+</tr>
+<tr>
+<td>GnomeVFSDrive</td>
+<td>GVolume</td>
+</tr>
+<tr>
+<td>-</td>
+<td>GDrive</td>
+</tr>
+<tr>
+<td>GnomeVFSContext</td>
+<td>GCancellable</td>
+</tr>
+<tr>
+<td>gnome_vfs_async_cancel</td>
+<td>g_cancellable_cancel</td>
+</tr>
+</tbody>
+</table></div>
+</div>
+<br class="table-break"><div class="section">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="id-1.5.4.2"></a>Before you start</h2></div></div></div>
+<a name="id-1.5.3.3"></a>Trash handling</h2></div></div></div>
+<p>
+        The handling of trashed files has been changed in GIO, compared
+        to gnome-vfs. gnome-vfs has a home-grown trash implementation that
+        predates the freedesktop.org <a class="ulink" href="http://www.freedesktop.org/wiki/Specifications/trash-spec" target="_top">Desktop Trash Can</a> specification
+        that is implemented in GIO. The location for storing trashed files
+        has changed from <code class="filename">$HOME/.Trash</code> to
+        <code class="filename">$HOME/.local/share/Trash</code> (or more correctly
+        <code class="filename">$XDG_DATA_HOME/Trash</code>), which means that
+        there is a need for migrating files that have been trashed by
+        gnome-vfs to the new location.
+      </p>
+<p>
+        In gnome-vfs, the <code class="filename">trash://</code> scheme offering a
+        merged view of all trash directories was implemented in nautilus,
+        and trash-handling applications had to find and monitor all trash
+        directories themselves. With GIO, the <code class="filename">trash://</code>
+        implementation has been moved to gvfs and applications can simply
+        monitor that location:
+      </p>
+<div class="informalexample">
+  <table class="listing_frame" border="0" cellpadding="0" cellspacing="0">
+    <tbody>
+      <tr>
+        <td class="listing_lines" align="right"><pre>1
+2
+3
+4
+5
+6
+7
+8
+9
+10
+11
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
+25
+26
+27
+28
+29
+30
+31
+32
+33
+34</pre></td>
+        <td class="listing_code"><pre class="programlisting"><span class="gtkdoc kwb">static void</span>
+<span class="function">file_changed</span> <span class="gtkdoc opt">(</span>GFileMonitor      <span class="gtkdoc opt">*</span>file_monitor<span class="gtkdoc opt">,</span>
+              GFile             <span class="gtkdoc opt">*</span>child<span class="gtkdoc opt">,</span>
+              GFile             <span class="gtkdoc opt">*</span>other_file<span class="gtkdoc opt">,</span>
+              GFileMonitorEvent  event_type<span class="gtkdoc opt">,</span>
+              gpointer           user_data<span class="gtkdoc opt">)</span>
+<span class="gtkdoc opt">{</span>
+  <span class="keyword">switch</span> <span class="gtkdoc opt">(</span>event_type<span class="gtkdoc opt">)</span>
+  <span class="gtkdoc opt">{</span>
+  <span class="keyword">case</span> G_FILE_MONITOR_EVENT_DELETED<span class="gtkdoc opt">:</span>
+    <span class="function"><a href="../glib/glib-Warnings-and-Assertions.html#g-print">g_print</a></span> <span class="gtkdoc opt">(</span><span class="string">&quot;'%s' removed from trash</span><span class="gtkdoc esc">\n</span><span class="string">&quot;</span><span class="gtkdoc opt">,</span> <span class="function"><a href="GFile.html#g-file-get-basename">g_file_get_basename</a></span> <span class="gtkdoc opt">(</span>child<span class="gtkdoc opt">));</span>
+    <span class="keyword">break</span><span class="gtkdoc opt">;</span>
+  <span class="keyword">case</span> G_FILE_MONITOR_EVENT_CREATED<span class="gtkdoc opt">:</span>
+    <span class="function"><a href="../glib/glib-Warnings-and-Assertions.html#g-print">g_print</a></span> <span class="gtkdoc opt">(</span><span class="string">&quot;'%s' added to trash</span><span class="gtkdoc esc">\n</span><span class="string">&quot;</span><span class="gtkdoc opt">,</span> <span class="function"><a href="GFile.html#g-file-get-basename">g_file_get_basename</a></span> <span class="gtkdoc opt">(</span>child<span class="gtkdoc opt">));</span>
+    <span class="keyword">break</span><span class="gtkdoc opt">;</span>
+  <span class="keyword">default</span><span class="gtkdoc opt">: ;</span>
+  <span class="gtkdoc opt">}</span>
+<span class="gtkdoc opt">}</span>
+<span class="gtkdoc kwb">static void</span>
+<span class="function">start_monitoring_trash</span> <span class="gtkdoc opt">(</span><span class="gtkdoc kwb">void</span><span class="gtkdoc opt">)</span>
+<span class="gtkdoc opt">{</span>
+  GFile <span class="gtkdoc opt">*</span>file<span class="gtkdoc opt">;</span>
+  GFileMonitor <span class="gtkdoc opt">*</span>monitor<span class="gtkdoc opt">;</span>
+  file <span class="gtkdoc opt">=</span> <span class="function"><a href="GFile.html#g-file-new-for-uri">g_file_new_for_uri</a></span> <span class="gtkdoc opt">(</span><span class="string">&quot;trash://&quot;</span><span class="gtkdoc opt">);</span>
+  monitor <span class="gtkdoc opt">=</span> <span class="function"><a href="GFile.html#g-file-monitor-directory">g_file_monitor_directory</a></span> <span class="gtkdoc opt">(</span>file<span class="gtkdoc opt">,</span> <span class="number">0</span><span class="gtkdoc opt">,</span> NULL<span class="gtkdoc opt">,</span> NULL<span class="gtkdoc opt">);</span>
+  <span class="function"><a href="../gobject/gobject-The-Base-Object-Type.html#g-object-unref">g_object_unref</a></span> <span class="gtkdoc opt">(</span>file<span class="gtkdoc opt">);</span>
+  <span class="function"><a href="../gobject/gobject-Signals.html#g-signal-connect">g_signal_connect</a></span> <span class="gtkdoc opt">(</span>monitor<span class="gtkdoc opt">,</span> <span class="string">&quot;changed&quot;</span><span class="gtkdoc opt">,</span> <span class="function"><a href="../gobject/gobject-Closures.html#G-CALLBACK:CAPS">G_CALLBACK</a></span> <span class="gtkdoc opt">(</span>file_changed<span class="gtkdoc opt">),</span> NULL<span class="gtkdoc opt">);</span>
+  <span class="comment">/* ... */</span>
+<span class="gtkdoc opt">}</span></pre></td>
+      </tr>
+    </tbody>
+  </table>
+</div>
 <p>
-        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.
+        GIO exposes some useful metadata about trashed files. There are
+        trash::orig-path and trash::deletion-date attributes. The
+        standard::icon attribute of the <code class="filename">trash://</code>
+        itself provides a suitable icon for displaying the trash can on
+        the desktop. If you are using this icon, make sure to monitor
+        this attribute for changes, since the icon may be updated to
+        reflect that state of the trash can.
       </p>
 <p>
-        It is always a good idea to have a look at how others have handled
-        similar problems before.
+        Moving a file to the trash is much simpler with GIO. Instead of
+        using <a href="/usr/share/gtk-doc/html/gnome-vfs-2.0/gnome-vfs-2.0-gnome-vfs-directory-find-ops.html#gnome-vfs-find-directory"><code class="function">gnome_vfs_find_directory()</code></a> with <a href="/usr/share/gtk-doc/html/gnome-vfs-2.0/gnome-vfs-2.0-gnome-vfs-directory-find-ops.html#GNOME-VFS-DIRECTORY-KIND-TRASH:CAPS"><code class="literal">GNOME_VFS_DIRECTORY_KIND_TRASH</code></a>
+        to find out where to move the trashed file, just use the <a class="link" href="GFile.html#g-file-trash" title="g_file_trash ()"><code class="function">g_file_trash()</code></a>
+        function.
       </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/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>