docs: switch to xi:inbclude for the content to save some more seconds

This commit is contained in:
Stefan Kost 2010-01-07 10:47:20 +02:00
parent 00db5238d9
commit 7211f7f8eb
7 changed files with 166 additions and 173 deletions

View File

@ -1,29 +1,6 @@
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
<!ENTITY gobject-GType SYSTEM "xml/gtype.xml">
<!ENTITY gobject-GTypePlugin SYSTEM "xml/gtypeplugin.xml">
<!ENTITY gobject-GTypeModule SYSTEM "xml/gtypemodule.xml">
<!ENTITY gobject-The-Base-Object-Type SYSTEM "xml/objects.xml">
<!ENTITY gobject-Enumeration-and-Flag-Types SYSTEM "xml/enumerations_flags.xml">
<!ENTITY gobject-Boxed-Types SYSTEM "xml/gboxed.xml">
<!ENTITY gobject-Generic-values SYSTEM "xml/generic_values.xml">
<!ENTITY gobject-param-value-types SYSTEM "xml/param_value_types.xml">
<!ENTITY gobject-GParamSpec SYSTEM "xml/gparamspec.xml">
<!ENTITY gobject-Varargs-Value-Collection SYSTEM "xml/value_collection.xml">
<!ENTITY gobject-Signals SYSTEM "xml/signals.xml">
<!ENTITY gobject-Closures SYSTEM "xml/gclosure.xml">
<!ENTITY gobject-Value-Arrays SYSTEM "xml/value_arrays.xml">
<!ENTITY glib-mkenums SYSTEM "glib-mkenums.xml">
<!ENTITY glib-genmarshal SYSTEM "glib-genmarshal.xml">
<!ENTITY gobject-query SYSTEM "gobject-query.xml">
<!ENTITY tutorial-Intro SYSTEM "tut_intro.xml">
<!ENTITY tutorial-GType SYSTEM "tut_gtype.xml">
<!ENTITY tutorial-GObject SYSTEM "tut_gobject.xml">
<!ENTITY tutorial-GSignal SYSTEM "tut_gsignal.xml">
<!ENTITY tutorial-HowTo SYSTEM "tut_howto.xml">
<!ENTITY tutorial-Tools SYSTEM "tut_tools.xml">
<!ENTITY % local.common.attrib "xmlns:xi CDATA #FIXED 'http://www.w3.org/2003/XInclude'"> <!ENTITY % local.common.attrib "xmlns:xi CDATA #FIXED 'http://www.w3.org/2003/XInclude'">
<!ENTITY version SYSTEM "version.xml"> <!ENTITY version SYSTEM "version.xml">
@ -85,46 +62,38 @@
<part label="I"> <part label="I">
<title>Concepts</title> <title>Concepts</title>
&tutorial-Intro; <xi:include href="tut_intro.xml" />
&tutorial-GType; <xi:include href="tut_gtype.xml" />
&tutorial-GObject; <xi:include href="tut_gobject.xml" />
&tutorial-GSignal; <xi:include href="tut_gsignal.xml" />
</part> </part>
<reference label="II"> <reference label="II">
<title>API Reference</title> <title>API Reference</title>
&gobject-GType; <xi:include href="xml/gtype.xml" />
&gobject-GTypePlugin; <xi:include href="xml/gtypeplugin.xml" />
&gobject-GTypeModule; <xi:include href="xml/gtypemodule.xml" />
&gobject-The-Base-Object-Type; <xi:include href="xml/objects.xml" />
&gobject-Enumeration-and-Flag-Types; <xi:include href="xml/enumerations_flags.xml" />
&gobject-Boxed-Types; <xi:include href="xml/gboxed.xml" />
&gobject-Generic-values; <xi:include href="xml/generic_values.xml" />
&gobject-param-value-types; <xi:include href="xml/param_value_types.xml" />
&gobject-Varargs-Value-Collection; <xi:include href="xml/gparamspec.xml" />
&gobject-GParamSpec; <xi:include href="xml/value_collection.xml" />
&gobject-Signals; <xi:include href="xml/signals.xml" />
&gobject-Closures; <xi:include href="xml/gclosure.xml" />
&gobject-Value-Arrays; <xi:include href="xml/value_arrays.xml" />
</reference> </reference>
<reference label="III"> <reference label="III">
<title>Tools Reference</title> <title>Tools Reference</title>
&glib-mkenums; <xi:include href="glib-mkenums.xml" />
&glib-genmarshal; <xi:include href="glib-genmarshal.xml" />
&gobject-query; <xi:include href="gobject-query.xml" />
</reference> </reference>
<part label="IV">
<title>Tutorial</title>
&tutorial-HowTo; <xi:include href="tut_howto.xml" />
</part> <xi:include href="tut_tools.xml" />
<part label="V">
<title>Related Tools</title>
&tutorial-Tools;
</part>
<index id="api-index-full"> <index id="api-index-full">
<title>Index</title> <title>Index</title>

View File

@ -1,4 +1,7 @@
<?xml version='1.0' encoding="ISO-8859-1"?> <?xml version='1.0' encoding="ISO-8859-1"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
]>
<chapter id="chapter-gobject"> <chapter id="chapter-gobject">
<title>The GObject base class</title> <title>The GObject base class</title>

View File

@ -1,4 +1,7 @@
<?xml version='1.0' encoding="ISO-8859-1"?> <?xml version='1.0' encoding="ISO-8859-1"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
]>
<chapter id="chapter-signal"> <chapter id="chapter-signal">
<title>The GObject messaging system</title> <title>The GObject messaging system</title>

View File

@ -1,4 +1,7 @@
<?xml version='1.0' encoding="ISO-8859-1"?> <?xml version='1.0' encoding="ISO-8859-1"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
]>
<chapter id="chapter-gtype"> <chapter id="chapter-gtype">
<title>The GLib Dynamic Type System</title> <title>The GLib Dynamic Type System</title>
@ -900,7 +903,7 @@ maman_ibaz_base_init (gpointer g_iface)
<para> <para>
The above process can be summarized as follows: The above process can be summarized as follows:
<table id="ginterface-init-table"> <table id="ginterface-fini-table">
<title>Interface Finalization</title> <title>Interface Finalization</title>
<tgroup cols="3"> <tgroup cols="3">
<colspec colwidth="*" colnum="1" align="left"/> <colspec colwidth="*" colnum="1" align="left"/>

View File

@ -1,11 +1,16 @@
<?xml version='1.0' encoding="ISO-8859-1"?> <?xml version='1.0' encoding="ISO-8859-1"?>
<partintro> <!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
]>
<part label="IV">
<title>Tutorial</title>
<partintro>
<para> <para>
This chapter tries to answer the real-life questions of users and presents This chapter tries to answer the real-life questions of users and presents
the most common scenario use cases I could come up with. the most common scenario use cases I could come up with.
The use cases are presented from most likely to less likely. The use cases are presented from most likely to less likely.
</para> </para>
</partintro> </partintro>
<chapter id="howto-gobject"> <chapter id="howto-gobject">
<title>How to define and implement a new GObject</title> <title>How to define and implement a new GObject</title>
@ -1712,4 +1717,4 @@ g_object_do_class_init (GObjectClass *class)
</sect2> </sect2>
--> -->
</part>

View File

@ -1,4 +1,7 @@
<?xml version='1.0' encoding="ISO-8859-1"?> <?xml version='1.0' encoding="ISO-8859-1"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
]>
<chapter id="chapter-intro"> <chapter id="chapter-intro">
<title>Background</title> <title>Background</title>

View File

@ -1,5 +1,11 @@
<?xml version='1.0' encoding="ISO-8859-1"?> <?xml version='1.0' encoding="ISO-8859-1"?>
<partintro> <!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
]>
<part label="V">
<title>Related Tools</title>
<partintro>
<para> <para>
Several useful developer tools have been build around GObject Several useful developer tools have been build around GObject
technology. The next sections briefly introduce them and link to technology. The next sections briefly introduce them and link to
@ -13,9 +19,9 @@
written to generate GObject skeleton form boilerplate code, or written to generate GObject skeleton form boilerplate code, or
even translating higher-level language into plain C. even translating higher-level language into plain C.
</para> </para>
</partintro> </partintro>
<chapter id="tools-vala"> <chapter id="tools-vala">
<title>Vala</title> <title>Vala</title>
<para> <para>
From the <ulink url="http://live.gnome.org/Vala">Vala From the <ulink url="http://live.gnome.org/Vala">Vala
@ -31,9 +37,9 @@
translates Vala into GObject C code. It can also compile translates Vala into GObject C code. It can also compile
non-GObject C, using plain C API. non-GObject C, using plain C API.
</para> </para>
</chapter> </chapter>
<chapter id="tools-gob"> <chapter id="tools-gob">
<title>GObject builder</title> <title>GObject builder</title>
<para> <para>
@ -47,9 +53,9 @@
Lex. The implementation is intentionally kept simple: the inline C Lex. The implementation is intentionally kept simple: the inline C
code provided by the user is not parsed. code provided by the user is not parsed.
</para> </para>
</chapter> </chapter>
<chapter id="tools-ginspector"> <chapter id="tools-ginspector">
<title>Graphical inspection of GObjects</title> <title>Graphical inspection of GObjects</title>
<para> <para>
@ -58,9 +64,9 @@
url="http://sourceforge.net/projects/g-inspector">G-Inspector</ulink>. It url="http://sourceforge.net/projects/g-inspector">G-Inspector</ulink>. It
is able to display GLib/GTK+ objects and their properties. is able to display GLib/GTK+ objects and their properties.
</para> </para>
</chapter> </chapter>
<chapter id="tools-refdb"> <chapter id="tools-refdb">
<title>Debugging reference count problems</title> <title>Debugging reference count problems</title>
<para> <para>
@ -86,9 +92,9 @@ static volatile GObject *g_trap_object_ref;
and <link linkend="g-object-unref">g_object_unref</link>() will be intercepted and <link linkend="g-object-unref">g_object_unref</link>() will be intercepted
when called with that value. when called with that value.
</para> </para>
</chapter> </chapter>
<chapter id="tools-gtkdoc"> <chapter id="tools-gtkdoc">
<title>Writing API docs</title> <title>Writing API docs</title>
<para>The API documentation for most of the GLib, GObject, GTK+ and GNOME <para>The API documentation for most of the GLib, GObject, GTK+ and GNOME
@ -100,7 +106,7 @@ static volatile GObject *g_trap_object_ref;
(a small program part of the libxslt library) to generate the final HTML (a small program part of the libxslt library) to generate the final HTML
output. Other tools can be used to generate PDF output from the source XML. output. Other tools can be used to generate PDF output from the source XML.
The following code excerpt shows what these comments look like. The following code excerpt shows what these comments look like.
<programlisting> <programlisting>
/** /**
* gtk_widget_freeze_child_notify: * gtk_widget_freeze_child_notify:
* @widget: a #GtkWidget * @widget: a #GtkWidget
@ -114,7 +120,7 @@ void
gtk_widget_freeze_child_notify (GtkWidget *widget) gtk_widget_freeze_child_notify (GtkWidget *widget)
{ {
... ...
</programlisting> </programlisting>
</para> </para>
<para> <para>
Thorough Thorough
@ -122,4 +128,5 @@ gtk_widget_freeze_child_notify (GtkWidget *widget)
on how to set up and use gtk-doc in your on how to set up and use gtk-doc in your
project is provided on the GNOME developer website. project is provided on the GNOME developer website.
</para> </para>
</chapter> </chapter>
</part>