glade3 r1776 - trunk/doc

[tvb svn gnome org]

Author: tvb
Date: Mon Apr  7 13:46:21 2008
New Revision: 1776
URL: http://svn.gnome.org/viewvc/glade3?rev=1776&view=rev

Log:
fixed a few minor errors (was missing the "parent" attribute
on widget classes)




Modified:
   trunk/doc/catalogintro.sgml
   trunk/doc/widgetclasses.sgml

Modified: trunk/doc/catalogintro.sgml
==============================================================================
--- trunk/doc/catalogintro.sgml	(original)
+++ trunk/doc/catalogintro.sgml	Mon Apr  7 13:46:21 2008
@@ -17,11 +17,13 @@
 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>

Modified: trunk/doc/widgetclasses.sgml
==============================================================================
--- trunk/doc/widgetclasses.sgml	(original)
+++ trunk/doc/widgetclasses.sgml	Mon Apr  7 13:46:21 2008
@@ -141,6 +141,18 @@
       </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>