RubyGems - atk - Versions diffs - 0.90.2-x86-mingw32 - Mend

atk 0.90.2-x86-mingw32

Files changed (849) hide show

data/vendor/local/share/gtk-doc/html/gobject/howto-gobject.html ADDED Viewed

@@ -0,0 +1,283 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>How to define and implement a new GObject</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GObject Reference Manual">
+<link rel="up" href="pt02.html" title="Part IV. Tutorial">
+<link rel="prev" href="pt02.html" title="Part IV. Tutorial">
+<link rel="next" href="howto-gobject-code.html" title="Boilerplate code">
+<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="pt02.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="pt02.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GObject Reference Manual</th>
+<td><a accesskey="n" href="howto-gobject-code.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="chapter" title="How to define and implement a new GObject">
+<div class="titlepage"><div><div><h2 class="title">
+<a name="howto-gobject"></a>How to define and implement a new GObject</h2></div></div></div>
+<div class="toc"><dl>
+<dt><span class="sect1"><a href="howto-gobject.html#howto-gobject-header">Boilerplate header code</a></span></dt>
+<dt><span class="sect1"><a href="howto-gobject-code.html">Boilerplate code</a></span></dt>
+<dt><span class="sect1"><a href="howto-gobject-construction.html">Object Construction</a></span></dt>
+<dt><span class="sect1"><a href="howto-gobject-destruction.html">Object Destruction</a></span></dt>
+<dt><span class="sect1"><a href="howto-gobject-methods.html">Object methods</a></span></dt>
+<dd><dl>
+<dt><span class="sect2"><a href="howto-gobject-methods.html#id597147">Non-virtual public methods</a></span></dt>
+<dt><span class="sect2"><a href="howto-gobject-methods.html#id597172">Virtual public methods</a></span></dt>
+<dt><span class="sect2"><a href="howto-gobject-methods.html#id597256">Virtual private Methods</a></span></dt>
+</dl></dd>
+<dt><span class="sect1"><a href="howto-gobject-chainup.html">Chaining up</a></span></dt>
+</dl></div>
+<p>
+    Clearly, this is one of the most common questions people ask: they just
+    want to crank code and implement a subclass of a GObject. Sometimes because
+    they want to create their own class hierarchy, sometimes because they want
+    to subclass one of GTK+'s widget. This chapter will focus on the
+    implementation of a subtype of GObject.
+  </p>
+<div class="sect1" title="Boilerplate header code">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="howto-gobject-header"></a>Boilerplate header code</h2></div></div></div>
+<p>
+      The first step before writing the code for your GObject is to write the
+      type's header which contains the needed type, function and macro
+      definitions. Each of these elements is nothing but a convention which
+      is followed not only by GTK+'s code but also by most users of GObject.
+      If you feel the need not to obey the rules stated below, think about it
+      twice:
+      </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>If your users are a bit accustomed to GTK+ code or any
+        GLib code, they will be a bit surprised and getting used to the
+        conventions you decided upon will take time (money) and will make them
+        grumpy (not a good thing)</p></li>
+<li class="listitem"><p>You must assess the fact that these conventions might
+        have been designed by both smart and experienced people: maybe they
+        were at least partly right. Try  to put your ego aside.</p></li>
+</ul></div>
+<p>
+    </p>
+<p>
+      Pick a name convention for your headers and source code and stick to it:
+      </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>use a dash to separate the prefix from the typename:
+        <code class="filename">maman-bar.h</code> and <code class="filename">maman-bar.c</code>
+        (this is the convention used by Nautilus and most GNOME libraries).</p></li>
+<li class="listitem"><p>use an underscore to separate the prefix from the
+        typename: <code class="filename">maman_bar.h</code> and
+        <code class="filename">maman_bar.c</code>.</p></li>
+<li class="listitem"><p>Do not separate the prefix from the typename:
+        <code class="filename">mamanbar.h</code> and <code class="filename">mamanbar.c</code>.
+        (this is the convention used by GTK+)</p></li>
+</ul></div>
+<p>
+      I personally like the first solution better: it makes reading file names
+      easier for those with poor eyesight like me.
+    </p>
+<p>
+      When you need some private (internal) declarations in several
+      (sub)classes, you can define them in a private header file which
+      is often named by appending the <span class="emphasis"><em>private</em></span> keyword
+      to the public header name. For example, one could use
+      <code class="filename">maman-bar-private.h</code>,
+      <code class="filename">maman_bar_private.h</code> or
+      <code class="filename">mamanbarprivate.h</code>. Typically, such private header
+      files are not installed.
+    </p>
+<p>
+      The basic conventions for any header which exposes a GType are described
+      in <a class="xref" href="gtype-conventions.html" title="Conventions">the section called “Conventions”</a>. Most GObject-based code also
+      obeys one of of the following conventions: pick one and stick to it.
+      </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
+<p>
+            If you want to declare a type named bar with prefix maman, name the type instance
+            <code class="function">MamanBar</code> and its class <code class="function">MamanBarClass</code>
+            (name is case-sensitive). It is customary to declare them with code similar to the
+            following:
+</p>
+<pre class="programlisting">
+/*
+ * Copyright/Licensing information.
+ */
+/* inclusion guard */
+#ifndef __MAMAN_BAR_H__
+#define __MAMAN_BAR_H__
+#include &lt;glib-object.h&gt;
+/*
+ * Potentially, include other headers on which this header depends.
+ */
+/*
+ * Type macros.
+ */
+#define MAMAN_TYPE_BAR                  (maman_bar_get_type ())
+#define MAMAN_BAR(obj)                  (G_TYPE_CHECK_INSTANCE_CAST ((obj), MAMAN_TYPE_BAR, MamanBar))
+#define MAMAN_IS_BAR(obj)               (G_TYPE_CHECK_INSTANCE_TYPE ((obj), MAMAN_TYPE_BAR))
+#define MAMAN_BAR_CLASS(klass)          (G_TYPE_CHECK_CLASS_CAST ((klass), MAMAN_TYPE_BAR, MamanBarClass))
+#define MAMAN_IS_BAR_CLASS(klass)       (G_TYPE_CHECK_CLASS_TYPE ((klass), MAMAN_TYPE_BAR))
+#define MAMAN_BAR_GET_CLASS(obj)        (G_TYPE_INSTANCE_GET_CLASS ((obj), MAMAN_TYPE_BAR, MamanBarClass))
+typedef struct _MamanBar        MamanBar;
+typedef struct _MamanBarClass   MamanBarClass;
+struct _MamanBar
+{
+  GObject parent_instance;
+  /* instance members */
+};
+struct _MamanBarClass
+{
+  GObjectClass parent_class;
+  /* class members */
+};
+/* used by MAMAN_TYPE_BAR */
+GType maman_bar_get_type (void);
+/*
+ * Method definitions.
+ */
+#endif /* __MAMAN_BAR_H__ */
+</pre>
+<p>
+          </p>
+</li>
+<li class="listitem">
+<p>
+            Most GTK+ types declare their private fields in the public header
+            with a /* private */ comment, relying on their user's intelligence
+            not to try to play with these fields. Fields not marked private
+            are considered public by default. The /* protected */ comment
+            (same semantics as those of C++) is also used, mainly in the GType
+            library, in code written by Tim Janik.
+</p>
+<pre class="programlisting">
+struct _MamanBar
+{
+  GObject parent_instance;
+  /*&lt; private &gt;*/
+  int hsize;
+};
+</pre>
+<p>
+          </p>
+</li>
+<li class="listitem">
+<p>
+            All of Nautilus code and a lot of GNOME libraries use private
+            indirection members, as described by Herb Sutter in his Pimpl
+            articles(see <a class="ulink" href="http://www.gotw.ca/gotw/024.htm" target="_top">Compilation Firewalls</a>
+            and <a class="ulink" href="http://www.gotw.ca/gotw/028.htm" target="_top">The Fast Pimpl Idiom</a>:
+            he summarizes the different issues better than I will).
+</p>
+<pre class="programlisting">
+typedef struct _MamanBarPrivate MamanBarPrivate;
+struct _MamanBar
+{
+  GObject parent_instance;
+  /*&lt; private &gt;*/
+  MamanBarPrivate *priv;
+};
+</pre>
+<p>
+            </p>
+<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
+<h3 class="title">Note</h3>
+<p>Do not call this <code class="varname">private</code>, as
+            that is a registered c++ keyword.</p>
+</div>
+<p>
+            The private structure is then defined in the .c file, using the
+            g_type_class_add_private() function to notify the presence of
+            a private memory area for each instance and it can either
+            be retrieved using <code class="function">G_TYPE_INSTANCE_GET_PRIVATE()</code>
+            each time is needed, or assigned to the <code class="literal">priv</code>
+            member of the instance structure inside the object's
+            <code class="function">init</code> function.
+</p>
+<pre class="programlisting">
+#define MAMAN_BAR_GET_PRIVATE(obj) (G_TYPE_INSTANCE_GET_PRIVATE ((obj), MAMAN_TYPE_BAR, MamanBarPrivate))
+struct _MamanBarPrivate
+{
+  int hsize;
+}
+static void
+maman_bar_class_init (MamanBarClass *klass)
+{
+  g_type_class_add_private (klass, sizeof (MamanBarPrivate));
+}
+static void
+maman_bar_init (MamanBar *self)
+{
+  MamanBarPrivate *priv;
+  self-&gt;priv = priv = MAMAN_BAR_GET_PRIVATE (self);
+  priv-&gt;hsize = 42;
+}
+</pre>
+<p>
+          </p>
+</li>
+<li class="listitem"><p>
+            You don't need to free or allocate the private structure, only the
+            objects or pointers that it may contain. Another advantage of this
+            to the previous version is that is lessens memory fragmentation,
+            as the public and private parts of the instance memory are
+            allocated at once.
+          </p></li>
+</ul></div>
+<p>
+    </p>
+<p>
+      Finally, there are different header include conventions. Again, pick one
+      and stick to it. I personally use indifferently any of the two, depending
+      on the codebase I work on: the rule, as always, is consistency.
+      </p>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem"><p>
+            Some people add at the top of their headers a number of #include
+            directives to pull in all the headers needed to compile client
+            code. This allows client code to simply #include "maman-bar.h".
+          </p></li>
+<li class="listitem"><p>
+            Other do not #include anything and expect the client to #include
+            themselves the headers they need before including your header. This
+            speeds up compilation because it minimizes the amount of
+            pre-processor work. This can be used in conjunction with the
+            re-declaration of certain unused types in the client code to
+            minimize compile-time dependencies and thus speed up compilation.
+          </p></li>
+</ul></div>
+<p>
+    </p>
+</div>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.14</div>
+</body>
+</html>

data/vendor/local/share/gtk-doc/html/gobject/howto-interface-implement.html ADDED Viewed

@@ -0,0 +1,125 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>How To define implement an Interface?</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GObject Reference Manual">
+<link rel="up" href="howto-interface.html" title="How to define and implement interfaces">
+<link rel="prev" href="howto-interface.html" title="How to define and implement interfaces">
+<link rel="next" href="ch06s03.html" title="Interface definition prerequisites">
+<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="howto-interface.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="howto-interface.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GObject Reference Manual</th>
+<td><a accesskey="n" href="ch06s03.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="sect1" title="How To define implement an Interface?">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="howto-interface-implement"></a>How To define implement an Interface?</h2></div></div></div>
+<p>
+      Once the interface is defined, implementing it is rather trivial.
+    </p>
+<p>
+      The first step is to define a normal GObject class, like:
+</p>
+<pre class="programlisting">
+#ifndef __MAMAN_BAZ_H__
+#define __MAMAN_BAZ_H__
+#include &lt;glib-object.h&gt;
+#define MAMAN_TYPE_BAZ             (maman_baz_get_type ())
+#define MAMAN_BAZ(obj)             (G_TYPE_CHECK_INSTANCE_CAST ((obj), MAMAN_TYPE_BAZ, Mamanbaz))
+#define MAMAN_IS_BAZ(obj)          (G_TYPE_CHECK_INSTANCE_TYPE ((obj), MAMAN_TYPE_BAZ))
+#define MAMAN_BAZ_CLASS(klass)     (G_TYPE_CHECK_CLASS_CAST ((klass), MAMAN_TYPE_BAZ, MamanbazClass))
+#define MAMAN_IS_BAZ_CLASS(klass)  (G_TYPE_CHECK_CLASS_TYPE ((klass), MAMAN_TYPE_BAZ))
+#define MAMAN_BAZ_GET_CLASS(obj)   (G_TYPE_INSTANCE_GET_CLASS ((obj), MAMAN_TYPE_BAZ, MamanbazClass))
+typedef struct _MamanBaz        MamanBaz;
+typedef struct _MamanBazClass   MamanBazClass;
+struct _MamanBaz
+{
+  GObject parent_instance;
+  int instance_member;
+};
+struct _MamanBazClass
+{
+  GObjectClass parent_class;
+};
+GType maman_baz_get_type (void);
+#endif /* __MAMAN_BAZ_H__ */
+</pre>
+<p>
+      There is clearly nothing specifically weird or scary about this header:
+      it does not define any weird API or derives from a weird type.
+    </p>
+<p>
+      The second step is to implement <span class="type">MamanBaz</span> by defining
+      its GType. Instead of using <code class="function">G_DEFINE_TYPE</code> we
+      use <code class="function">G_DEFINE_TYPE_WITH_CODE</code> and the
+      <code class="function">G_IMPLEMENT_INTERFACE</code> macros.
+</p>
+<pre class="programlisting">
+static void maman_ibaz_interface_init (MamanIbazInterface *iface);
+G_DEFINE_TYPE_WITH_CODE (MamanBar, maman_bar, G_TYPE_OBJECT,
+                         G_IMPLEMENT_INTERFACE (MAMAN_TYPE_IBAZ,
+                                                maman_ibaz_interface_init));
+</pre>
+<p>
+      This definition is very much like all the similar functions we looked
+      at previously. The only interface-specific code present here is the call
+      to <code class="function">G_IMPLEMENT_INTERFACE</code>.
+    </p>
+<div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;">
+<h3 class="title">Note</h3>
+<p>Classes can implement multiple interfaces by using multiple
+    calls to <code class="function">G_IMPLEMENT_INTERFACE</code> inside the call
+    to <code class="function">G_DEFINE_TYPE_WITH_CODE</code>.</p>
+</div>
+<p>
+      <code class="function">maman_baz_interface_init</code>, the interface
+      initialization function: inside it every virtual method of the interface
+      must be assigned to its implementation:
+</p>
+<pre class="programlisting">
+static void
+maman_baz_do_action (MamanBaz *self)
+{
+  g_print ("Baz implementation of IBaz interface Action: 0x%x.\n",
+           self-&gt;instance_member);
+}
+static void
+maman_ibaz_interface_init (MamanIbazInterface *iface)
+{
+  iface-&gt;do_action = baz_do_action;
+}
+static void
+maman_baz_init (MamanBaz *self)
+{
+  MamanBaz *self = MAMAN_BAZ (instance);
+  self-&gt;instance_member = 0xdeadbeaf;
+}
+</pre>
+<p>
+    </p>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.14</div>
+</body>
+</html>

data/vendor/local/share/gtk-doc/html/gobject/howto-interface-properties.html ADDED Viewed

@@ -0,0 +1,167 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
+<title>Interface Properties</title>
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
+<link rel="home" href="index.html" title="GObject Reference Manual">
+<link rel="up" href="howto-interface.html" title="How to define and implement interfaces">
+<link rel="prev" href="ch06s03.html" title="Interface definition prerequisites">
+<link rel="next" href="howto-signals.html" title="How to create and use signals">
+<meta name="generator" content="GTK-Doc V1.14 (XML mode)">
+<link rel="stylesheet" href="style.css" type="text/css">
+</head>
+<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
+<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
+<td><a accesskey="p" href="ch06s03.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
+<td><a accesskey="u" href="howto-interface.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
+<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
+<th width="100%" align="center">GObject Reference Manual</th>
+<td><a accesskey="n" href="howto-signals.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
+</tr></table>
+<div class="sect1" title="Interface Properties">
+<div class="titlepage"><div><div><h2 class="title" style="clear: both">
+<a name="howto-interface-properties"></a>Interface Properties</h2></div></div></div>
+<p>
+      Starting from version 2.4 of GLib, GObject interfaces can also have
+      properties. Declaration of the interface properties is similar to
+      declaring the properties of ordinary GObject types as explained in
+      <a class="xref" href="gobject-properties.html" title="Object properties">the section called “Object properties”</a>,
+      except that <code class="function"><a class="link" href="gobject-The-Base-Object-Type.html#g-object-interface-install-property" title="g_object_interface_install_property ()">g_object_interface_install_property</a></code> is used to
+      declare the properties instead of <code class="function"><a class="link" href="gobject-The-Base-Object-Type.html#g-object-class-install-property" title="g_object_class_install_property ()">g_object_class_install_property</a></code>.
+    </p>
+<p>
+      To include a property named 'name' of type <span class="type">string</span> in the
+      <span class="type">maman_ibaz</span> interface example code above, we only need to
+      add one
+      <sup>[<a name="id604902" href="#ftn.id604902" class="footnote">12</a>]</sup>
+      line in the <code class="function">maman_ibaz_base_init</code>
+      <sup>[<a name="id604915" href="#ftn.id604915" class="footnote">13</a>]</sup>
+      as shown below:
+</p>
+<pre class="programlisting">
+static void
+maman_ibaz_base_init (gpointer g_iface)
+{
+  static gboolean is_initialized = FALSE;
+  if (!is_initialized)
+    {
+      g_object_interface_install_property (g_iface,
+                                           g_param_spec_string ("name",
+                                                                "Name",
+                                                                "Name of the MamanIbaz",
+                                                                "maman",
+                                                                G_PARAM_READWRITE));
+      is_initialized = TRUE;
+    }
+}
+</pre>
+<p>
+    </p>
+<p>
+      One point worth noting is that the declared property wasn't assigned an
+      integer ID. The reason being that integer IDs of properties are used
+      only inside the get and set methods and since interfaces do not
+      implement properties, there is no need to assign integer IDs to
+      interface properties.
+    </p>
+<p>
+      An implementation shall declare and define it's properties in the usual
+      way as explained in <a class="xref" href="gobject-properties.html" title="Object properties">the section called “Object properties”</a>, except for one
+      small change: it must declare the properties of the interface it
+      implements using <code class="function"><a class="link" href="gobject-The-Base-Object-Type.html#g-object-class-override-property" title="g_object_class_override_property ()">g_object_class_override_property</a></code>
+      instead of <code class="function"><a class="link" href="gobject-The-Base-Object-Type.html#g-object-class-install-property" title="g_object_class_install_property ()">g_object_class_install_property</a></code>.
+      The following code snippet shows the modifications needed in the
+      <span class="type">MamanBaz</span> declaration and implementation above:
+</p>
+<pre class="programlisting">
+struct _MamanBaz
+{
+  GObject parent_instance;
+  gint instance_member;
+  gchar *name;
+};
+enum
+{
+  PROP_0,
+  PROP_NAME
+};
+static void
+maman_baz_set_property (GObject      *object,
+                        guint         property_id,
+                        const GValue *value,
+                        GParamSpec   *pspec)
+{
+  MamanBaz *baz = MAMAN_BAZ (object);
+  GObject *obj;
+  switch (prop_id)
+    {
+    case ARG_NAME:
+      g_free (baz-&gt;name);
+      baz-&gt;name = g_value_dup_string (value);
+      break;
+    default:
+      G_OBJECT_WARN_INVALID_PROPERTY_ID (object, prop_id, pspec);
+      break;
+    }
+}
+static void
+maman_baz_get_property (GObject    *object,
+                        guint       prop_id,
+                        GValue     *value,
+                        GParamSpec *pspec)
+{
+  MamanBaz *baz = MAMAN_BAZ (object);
+  switch (prop_id)
+    {
+    case ARG_NAME:
+      g_value_set_string (value, baz-&gt;name);
+      break;
+    default:
+      G_OBJECT_WARN_INVALID_PROPERTY_ID (object, prop_id, pspec);
+      break;
+    }
+}
+static void
+maman_baz_class_init (MamanBazClass *klass)
+{
+  GObjectClass *gobject_class = G_OBJECT_CLASS (klass);
+  gobject_class-&gt;set_property = maman_baz_set_property;
+  gobject_class-&gt;get_property = maman_baz_get_property;
+  g_object_class_override_property (gobject_class, PROP_NAME, "name");
+}
+</pre>
+<p>
+    </p>
+<div class="footnotes">
+<br><hr width="100" align="left">
+<div class="footnote"><p><sup>[<a name="ftn.id604902" href="#id604902" class="para">12</a>] </sup>
+          That really is one line extended to six for the sake of clarity
+        </p></div>
+<div class="footnote"><p><sup>[<a name="ftn.id604915" href="#id604915" class="para">13</a>] </sup>
+          The <code class="function"><a class="link" href="gobject-The-Base-Object-Type.html#g-object-interface-install-property" title="g_object_interface_install_property ()">g_object_interface_install_property</a></code>
+          can also be called from <code class="function">class_init</code> but it must
+          not be called after that point.
+        </p></div>
+</div>
+</div>
+<div class="footer">
+<hr>
+          Generated by GTK-Doc V1.14</div>
+</body>
+</html>