Home | History | Annotate | Download | only in doc

Lines Matching full:glib

85             based on particular application frameworks.  For example, libdbus-glib and
248 different for GLib vs. Qt vs. Python applications, however.
312 just as it is in GLib or Qt or Java. Interfaces define the
706 <sect1 id="glib-client">
707 <title>GLib API: Using Remote Objects</title>
710 The GLib binding is defined in the header file
711 <literal>&lt;dbus/dbus-glib.h&gt;</literal>.
714 <sect2 id="glib-typemappings">
715 <title>D-Bus - GLib type mappings</title>
717 The heart of the GLib bindings for D-Bus is the mapping it
718 provides between D-Bus "type signatures" and GLib types
722 <sect3 id="glib-basic-typemappings">
752 <entry>Will be changed to a <literal>G_TYPE_INT16</literal> once GLib has it</entry>
757 <entry>Will be changed to a <literal>G_TYPE_UINT16</literal> once GLib has it</entry>
762 <entry>Will be changed to a <literal>G_TYPE_INT32</literal> once GLib has it</entry>
767 <entry>Will be changed to a <literal>G_TYPE_UINT32</literal> once GLib has it</entry>
800 <sect3 id="glib-container-typemappings">
815 type. The approach the GLib bindings take is pragmatic; try
822 corresponding built-in GLib type are mapped using that type:
858 types is a <literal>GArray</literal>. Now, GLib does not
865 The approach taken is to create these types in the D-Bus GLib
867 In the future, we hope to include such "fundamental" types in GLib
945 type by bindings. The obvious GLib mapping here is GHashTable. Again,
979 <sect3 id="glib-generic-typemappings">
997 <para>Here is a D-Bus program using the GLib bindings.
1061 <sect2 id="glib-program-setup">
1072 <sect2 id="glib-method-invocation">
1091 <sect2 id="glib-signal-connection">
1105 <application>glib-genmarshal</application>, and then register
1109 <sect2 id="glib-error-handling">
1112 All of the GLib binding methods such as
1132 "name" and a "message". The GLib bindings store this
1152 <sect2 id="glib-more-examples">
1154 <sect3 id="glib-sending-stuff">
1173 <sect3 id="glib-sending-hash">
1195 <sect3 id="glib-receiving-bool-int">
1216 <sect3 id="glib-sending-str-arrays">
1246 <sect3 id="glib-getting-str-array">
1270 <sect3 id="glib-sending-variant">
1291 glib-receiving-variant">
1315 <sect2 id="glib-generated-bindings">
1340 Run <literal>dbus-binding-tool --mode=glib-client
1343 file. For example: <command>dbus-binding-tool --mode=glib-client
1380 linkend="glib-server"/>), the exact behaviour of the client-side
1383 <literal>org.freedesktop.DBus.GLib.NoReply</literal>, which sets the
1393 <sect1 id="glib-server">
1394 <title>GLib API: Implementing Objects</title>
1399 be obviated by the upcoming GLib introspection support.
1410 &lt;annotation name="org.freedesktop.DBus.GLib.CSymbol" value="my_object"/&gt;
1413 &lt;annotation name="org.freedesktop.DBus.GLib.CSymbol" value="my_object_many_args"/&gt;
1435 Once you have written this XML, run <literal>dbus-binding-tool --mode=glib-server <replaceable>FILENAME</replaceable> &gt; <replaceable>HEADER_NAME</replaceable>.</literal> to
1436 generate a header file. For example: <command>dbus-binding-tool --mode=glib-server my-object.xml &gt; my-object-glue.h</command>.
1496 <sect2 id="glib-annotations">
1501 <literal>org.freedesktop.DBus.GLib.CSymbol</literal> but there are other
1505 <term><literal>org.freedesktop.DBus.GLib.CSymbol</literal></term>
1515 <term><literal>org.freedesktop.DBus.GLib.Async</literal></term>
1561 <term><literal>org.freedesktop.DBus.GLib.Const</literal></term>
1573 <term><literal>org.freedesktop.DBus.GLib.ReturnVal</literal></term>
1609 &lt;annotation name="org.freedesktop.DBus.GLib.ReturnVal" value=""/&gt;
1625 &lt;annotation name="org.freedesktop.DBus.GLib.ReturnVal" value="error"/&gt;
1846 Python. Here is an example using the GLib/GTK+ mainloop.
1851 import dbus.glib
1876 You will also notice that I check the version of the dbus bindings before importing dbus.glib. In older versions
1877 glib was the only available mainloop. As of version 0.41.0 we split out the glib dependency to allow for other mainloops
1880 While the glib mainloop is the only mainloop currently implemented, integrating other mainloops should
1895 import dbus.glib
2009 import dbus.glib
2038 import dbus.glib
2112 import dbus.glib