From 138e17cce0ab1051ff4f7b6d60521c70beb0269c Mon Sep 17 00:00:00 2001 From: Havoc Pennington Date: Tue, 10 Aug 2004 02:18:37 +0000 Subject: add a couple of notes about libdbus vs. bindings --- README | 8 ++++++++ doc/dbus-tutorial.xml | 4 +++- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/README b/README index 4e39c264..a26dbb29 100644 --- a/README +++ b/README @@ -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. -- cgit