summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorTristan Van Berkom <tvb@src.gnome.org>2008-04-07 12:46:21 +0000
committerTristan Van Berkom <tvb@src.gnome.org>2008-04-07 12:46:21 +0000
commit636521d77c1b1aed3ff2823d54bac2d63abcf151 (patch)
treed29a0890ce4c6f0da7d21b5dcbf49ac95167bce8 /doc
parentc43aaea090997a285ece539bf9b9f4bfbe057382 (diff)
downloadglade-636521d77c1b1aed3ff2823d54bac2d63abcf151.tar.gz
fixed a few minor errors (was missing the "parent" attribute
on widget classes) svn path=/trunk/; revision=1776
Diffstat (limited to 'doc')
-rw-r--r--doc/catalogintro.sgml12
-rw-r--r--doc/widgetclasses.sgml12
2 files changed, 19 insertions, 5 deletions
diff --git a/doc/catalogintro.sgml b/doc/catalogintro.sgml
index a31153b0..f30e2854 100644
--- a/doc/catalogintro.sgml
+++ b/doc/catalogintro.sgml
@@ -17,11 +17,13 @@ How to write and install a catalog
You can provide support for your custom widgets in a few ways, you can
make a package and install it to the system directories, load additional
catalogs in user directories, project directories for example, and
-you can optionally provide code support and/or icons, if you dont provide
-icons for the inspector and palette Glade will simply print a warning
-and use a default icon. The catalog file is written in an XML format and
-a DTD for the format can be found in the plugins/ directory of the Glade
-tarball.
+you can optionally provide code support and/or icons, normally you need
+to at least have the object type in a library somewhere, but you can work
+around this using the 'parent' property described in the next section.
+If you dont provide icons for the inspector and palette Glade will simply
+print a warning and use a default icon. The catalog file is written in an
+XML format and a DTD for the format can be found in the plugins/ directory
+of the Glade tarball.
</para>
<para>
diff --git a/doc/widgetclasses.sgml b/doc/widgetclasses.sgml
index f3f2d99e..bdc3d0ab 100644
--- a/doc/widgetclasses.sgml
+++ b/doc/widgetclasses.sgml
@@ -141,6 +141,18 @@ tree and will be translated before use in the interface.
</varlistentry>
<varlistentry>
+ <term>parent</term>
+ <listitem>
+ <para>
+Use this to specify the name of the parent your widget derives from, you
+can use this option instead of loading a real widget type (this allows you
+to fake derive and still add properties and run your catalog independantly
+of any plugins or libraries).
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
<term>toplevel</term>
<listitem>
<para>