[Decibel] DBus xml troubles

[Tobias Hunger]

Hello there!

I promised to keep you guys here more informed... so this is what I did this 
week:

I tried to start on Qt4 bindings to telepathy. This task is somewhat more 
involved than I had originally anticipated:-)

The good news is that oggis_ at #telepathy is already working on similar 
bindings. So far we did not find a time where both of us were available to 
stick our heads together. He says he did not get much done yet, so I decided 
to get started myself, hoping that we can pool our work later.

The first surprise to me was that there is no offical set of XML files 
describing the telepathy DBus interfaces. I was told at #telepathy that the 
spec itself is extracted from the python docstrings of an implementation of 
the specification and was asked to write up my own set of XML files, using 
those generated for the glib API of telepathy as a base. Those do not yet 
contain the newest features described in the spec, but it is rumored that 
there are some addons that did not make it into the spec itself yet. I 
decided to just use the libtelepathy stuff for now..

So I got some XML files and added annotations for the complex datatypes used 
(like "a(susv)" in the ConnectionManager). Those annotations map a DBus 
datatype to a Qt class that is meant to handle it and is required by 
dbusxml2cpp.

This does indeed produce some code, but unfortunately only for the first 
annotated member of the object processed:-( I'm currently trying to find out 
whether it is me doing something wrong again or a bug in dbusxml2cpp...

Are there any DBus gurus around that happen to know how to work around this 
problem?

I think I'll write a DBus Qt4 bindings howto once I got the first cset of 
bindings classes up and running! So far I have not found any documentation on 
how to do this.

Best Regards,

-- 

Tobias Hunger
Entwickler

basysKom GmbH
Robert-Bosch-Str. 7 | 64293 Darmstadt | Germany
Tel: +49 6151 3968769 | Fax: -736 |
tobias.hunger at basyskom.de | www.basyskom.de