This will generate org.kde.my_cool_interface.xml from my_awesome_header_file.h and install it in ${DBUS_INTERFACES_INSTALL_DIR}, wich usally means /usr/share/dbus-1/interfaces

+

This will generate org.kde.my_cool_interface.xml from my_awesome_header_file.h and install it in ${DBUS_INTERFACES_INSTALL_DIR} (wich usally means /usr/share/dbus-1/interfaces).

−

Note: "my_nice_target" is an already existing target of your project. Adding the xml as a dependency of it is a workaround to cause the xml file to be generated.

+

Note: Adding the xml as a source of your project (in first line, assuming your project sources are in a variable called my_nice_project_SRC) is a workaround to cause the xml file to be a dependency and thus to be generated.

−

=== CMake ===

+

=== Export the interface using CMake ===

Next we add this XML file to our project. This is done by adding the following line to the CMakeLists.txt file:

Next we add this XML file to our project. This is done by adding the following line to the CMakeLists.txt file:

D-Bus interfaces generally reflect the API of one or more classes in the providing application. Bridging this API over to D-Bus is done using by creating a QDBusAbstractAdaptor subclass that reacts to DBus messages and takes action directly. Usually, however, this simply results in one line methods that call similarly named methods in another object. This repetitive work can almost always be avoided by generating a D-Bus XML description file.

An interface as seen on the bus can be described using a standard XML format that is described in the D-Bus specification.

If one has used a D-Bus application such as qdbus or dbus-viewer to explore the org.freedesktop.DBus.Introspectable.Introspect method, the above might look familiar.

One can construct this XML by hand and manually map it to the API of a given class, but not only is this error prone and time consuming it's not much fun. If it weren't for the fact that this XML can be used by other applications wishing to consume your D-Bus interface, one may as well write their own QDBusAbstractAdaptor

Fortunately there are ways to automate the process so that it's hardly noticeable, namely: creating a class that includes the methods we wish to expose via D-Bus and using tools that come with Qt to do the rest for us.

We will be using the (fictitious) example of an interface that lets the user set the background wallpaper and query the current settings. We will be providing three methods in this interface, which can be seen in the following class definition:

#include <QObject>

class Background :QObject

{

Q_OBJECT

public:

Background(QObject* parent);

void doNotExportToDBus();

void refreshBackground();

QString currentBackground();

Q_SIGNALS:

void doNotExportThisSignal();

void backgroundChanged();

publicQ_SLOTS:

bool setBackground(QString name);

protectedQ_SLOTS:

void dbusCanNotSeeMe();

};

Next we need to mark which of the above methods we wish to expose via D-Bus. Fortunately, this is quite simple with the following options available to us:

export all signals

export all public slots

export all properties

export only scriptable signals

export only scriptable public slots

export only scriptable properties

We can also combine the above as we wish. To achieve the desired results in the above example then, we might adjust the class definition thusly:

Note how we moved the methods we wish to export to to be public slots and marked the signal we want to export with Q_SCRIPTABLE. We will later then choose to create an interface that exports all the public slots and all scriptable signals.

We would then go about creating an implementation of this class as defined above.

Tip

When exposing an API to other applications via D-Bus other applications and users, via scripting, may come to rely on the calls available in the interface. Changing the D-Bus interface can therefore cause breakage for others. For this reason it is recommended to keep compatibility with publicly advertised D-Bus APIs over the lifespan of a major release of your application.

The next step after having defined our interface is to come up with a name that it will appear as on the bus. These names by convention take on the form of reverse domain names so as to prevent name collisions. Therefore if the domain for your project website is http://foo.org you should prefix your interface names with org.foo. This is a very common approach to namespacing such exported components.

Therefore, we may choose to call our interface example org.foo.Background. The easiest way to define this is to add a Q_CLASSINFO macro entry to our class definition:

Now that we have set up the interface in our class, we will want to generate an adaptor class that mediates between D-Bus and our application's objects. The first step is to generate the XML seen at the outset of this tutorial.

To generate the XML we will be using the qdbuscpp2xml command line tool that comes with Qt. This program takes a C++ source file and generates a D-Bus XML definition of the interface for us. It lets us to define which methods to export using the following command line switches:

qdbuscpp2xml switches

Switch

Exports

-S

all signals

-M

all public slots

-P

all properties

-A

all exportable items

-s

scriptable signals

-m

scriptable public slots

-p

scriptable properties

-a

all scriptable items

In our example above we want to export all the public slots but only scriptable signals. Therefore we would use this command line:

$> qdbuscpp2xml -M-s background.h -o org.foo.Background.xml

This produces a file named org.foo.Background.xml which contains this:

This will generate org.kde.my_cool_interface.xml from my_awesome_header_file.h and install it in ${DBUS_INTERFACES_INSTALL_DIR} (wich usally means /usr/share/dbus-1/interfaces).

Note: Adding the xml as a source of your project (in first line, assuming your project sources are in a variable called my_nice_project_SRC) is a workaround to cause the xml file to be a dependency and thus to be generated.

This will cause two files, in this case backgroundadaptor.h and backgroundadaptor.cpp, to be generated in the build directory, built and added to the application at build time. You should not ship these files with your project's source distribution.

The generated class will take a Background* in its constructor and will include background.h.

The D-Bus XML description file will also be installed. This allows users to examine it as a reference and other applications to use this file to generate interface classes using qdbusxml2cpp as seen in the tutorial on accessing D-Bus interfaces.

Note

As of CMake 2.4.6, the qt4_add_dbus_adaptor macro is not part of the standard CMake distribution and requires the KDE4 SVN version of FindQt4.cmake. A version of FindQt4.cmake including qt4_add_dbus_adaptor is bound to eventually be included in CMake.

Now that we have our interface created for us, all we need to do is create it at runtime. We do this by including the generated header file and instantiating an object, as seen in this example:

#include "background.h"

#include "backgroundadaptor.h"

Background::Background(QObject* parent)

:QObject(parent)

{

new BackgroundAdaptor(this);

QDBusConnection dbus =QDBusConnection::sessionBus();

dbus.registerObject("/Background",this);

dbus.registerService("org.foo.Background");

}

It's that simple. Since the generated adaptor is a QObject when we pass it this it not only will be deleted when our Background object is deleted but it will bind itself to this for the purposes of forwarding D-Bus calls.

We then need to register our object on the bus by calling QDBusConnection::registerObject and expose the interface for others to use by calling QDBusConnection::registerService.

Tip

If there will be more than one of the same object created in your application then you will need to register each object with a unique path. If there is no well defined, unique naming scheme for your objects the this pointer may come in handy.