diff options
author | Havoc Pennington <hp@redhat.com> | 2004-08-10 02:18:37 +0000 |
---|---|---|
committer | Havoc Pennington <hp@redhat.com> | 2004-08-10 02:18:37 +0000 |
commit | 138e17cce0ab1051ff4f7b6d60521c70beb0269c (patch) | |
tree | 38fb14d27ec51957af487c02c37107e7844b0037 | |
parent | 7cb72cf53d8185b6df2b34701b44f4a2fb40224b (diff) | |
download | dbus-138e17cce0ab1051ff4f7b6d60521c70beb0269c.tar.gz |
add a couple of notes about libdbus vs. bindings
-rw-r--r-- | README | 8 | ||||
-rw-r--r-- | doc/dbus-tutorial.xml | 4 |
2 files changed, 11 insertions, 1 deletions
@@ -5,6 +5,14 @@ See also the file HACKING for notes of interest to developers working on D-BUS. See http://www.freedesktop.org/software/dbus/ for lots of documentation, mailing lists, etc. +Note +=== + +A core concept of the D-BUS implementation is that "libdbus" is +intended to be a low-level API, similar to Xlib. Most programmers are +intended to use the bindings to GLib, Qt, Python, Mono, Java, or +whatever. These bindings have varying levels of completeness. + Configuration flags === diff --git a/doc/dbus-tutorial.xml b/doc/dbus-tutorial.xml index 6f25289e..2bb67a4e 100644 --- a/doc/dbus-tutorial.xml +++ b/doc/dbus-tutorial.xml @@ -50,7 +50,9 @@ application frameworks. For example, libdbus-glib and libdbus-qt. There are also bindings to languages such as Python. These wrapper libraries are the API most people should use, - as they simplify the details of D-BUS programming. + as they simplify the details of D-BUS programming. libdbus is + intended to be a low-level backend for the higher level bindings. + Much of the libdbus API is only useful for binding implementation. </para> </listitem> </itemizedlist> |