[glib] docs: Mention GtkApplication in the GResource documentation

[Philip Withnall <pwithnall src gnome org>]

commit c7d325733c6a3bd384df6523350d9312df5ccc92
Author: Philip Withnall <withnall endlessm com>
Date:   Wed May 31 11:08:55 2017 +0100

    docs: Mention GtkApplication in the GResource documentation
    
    Since GtkApplication auto-loads some well-known resource paths. Add a
    cross-reference to its documentation. (The cross-reference won’t be
    linked if the GTK+ documentation isn’t available at build time, but this
    is probably good enough. It is likely to be available.)
    
    Signed-off-by: Philip Withnall <withnall endlessm com>
    
    https://bugzilla.gnome.org/show_bug.cgi?id=782336

 gio/gresource.c |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)
---
diff --git a/gio/gresource.c b/gio/gresource.c
index 117fe8c..9e1d481 100644
--- a/gio/gresource.c
+++ b/gio/gresource.c
@@ -133,6 +133,10 @@ G_DEFINE_BOXED_TYPE (GResource, g_resource, g_resource_ref, g_resource_unref)
  * to the data. You can also use URIs like "resource:///org/gtk/Example/data/splashscreen.png" with #GFile 
to access
  * the resource data.
  *
+ * Some higher-level APIs, such as #GtkApplication, will automatically load
+ * resources from certain well-known paths in the resource namespace as a
+ * convenience. See the documentation for those APIs for details.
+ *
  * There are two forms of the generated source, the default version uses the compiler support for constructor
  * and destructor functions (where available) to automatically create and register the #GResource on startup
  * or library load time. If you pass `--manual-register`, two functions to register/unregister the resource 
are created