Commit 0c10536d authored by Matthias Clasen's avatar Matthias Clasen Committed by Matthias Clasen

s/Gnome/GNOME/g (#352156, Guillaume Desmottes)

2006-12-14  Matthias Clasen  <mclasen@redhat.com>

        * gobject/*.xml: s/Gnome/GNOME/g (#352156, Guillaume Desmottes)
parent dc78f9b2
2006-12-14 Matthias Clasen <mclasen@redhat.com>
* gobject/*.xml: s/Gnome/GNOME/g (#352156, Guillaume Desmottes)
* glib/tmpl/keyfile.sgml: Clarify the behaviour
wrt. to duplicate keys and groups.
......
......@@ -17,7 +17,7 @@
<listitem><para>Generic per-object properties with set/get function pairs</para></listitem>
<listitem><para>Easy use of signals</para></listitem>
</itemizedlist>
All the GTK+ objects and all of the objects in Gnome libraries which use the GLib type
All the GTK+ objects and all of the objects in GNOME libraries which use the GLib type
system inherit from <type><link linkend="GObject">GObject</link></type> which is why it is important to understand
the details of how it works.
</para>
......
......@@ -7,7 +7,7 @@
<para>
Closures are central to the concept of asynchronous signal delivery
which is widely used throughout GTK+ and Gnome applications. A Closure is an
which is widely used throughout GTK+ and GNOME applications. A Closure is an
abstraction, a generic representation of a callback. It is a small structure
which contains three objects:
<itemizedlist>
......@@ -161,7 +161,7 @@ g_cclosure_marshal_VOID__INT (GClosure *closure,
This python marshaller transforms the input GValue list representing the function
parameters into a Python tuple which is the equivalent structure in python (you can
look in <function>pyg_closure_marshal</function> in <filename>pygtype.c</filename>
in the <emphasis>pygobject</emphasis> module in Gnome cvs server).
in the <emphasis>pygobject</emphasis> module in GNOME cvs server).
</para>
</sect2>
......
......@@ -61,7 +61,7 @@
<itemizedlist>
<listitem><para>
use a dash to separate the prefix from the typename: <filename>maman-bar.h</filename> and
<filename>maman-bar.c</filename> (this is the convention used by Nautilus and most Gnome libraries).
<filename>maman-bar.c</filename> (this is the convention used by Nautilus and most GNOME libraries).
</para></listitem>
<listitem><para>
use an underscore to separate the prefix from the typename: <filename>maman_bar.h</filename> and
......@@ -150,7 +150,7 @@ struct _MamanBar {
</programlisting>
</para></listitem>
<listitem><para>
All of Nautilus code and a lot of Gnome libraries use private indirection members, as described
All of Nautilus code and a lot of GNOME libraries use private indirection members, as described
by Herb Sutter in his Pimpl articles
(see <ulink url="http://www.gotw.ca/gotw/024.htm">Compilation Firewalls</ulink>
and <ulink url="http://www.gotw.ca/gotw/028.htm">The Fast Pimpl Idiom</ulink>
......@@ -1653,8 +1653,8 @@ klass->write_signal_id =
<title>Warning on signal creation and default closure</title>
<para>
Most of the existing code I have seen up to now (in both GTK+, Gnome libraries and
many GTK+ and Gnome applications) using signals uses a small
Most of the existing code I have seen up to now (in both GTK+, GNOME libraries and
many GTK+ and GNOME applications) using signals uses a small
variation of the default handler pattern I have shown in the previous section.
</para>
......
......@@ -2,7 +2,7 @@
<title>Background</title>
<para>
GObject, and its lower-level type system, GType, are used by GTK+ and most Gnome libraries to
GObject, and its lower-level type system, GType, are used by GTK+ and most GNOME libraries to
provide:
<itemizedlist>
<listitem><para>object-oriented C-based APIs and</para></listitem>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment