[Kde-hardware-devel] Bluetooth, anybody?

Tom Patzig tpatzig at suse.de
Tue Jan 13 16:46:47 CET 2009


Guillaume Pothier wrote:
> On Tue, Jan 13, 2009 at 9:54 AM, Bart Cerneels <bart.cerneels at kde.org> wrote:
>   
>> To get the device enumerations you mean? OpenObex will enumerate USB
>> devices for you or allow you to use BT addresses or IP-addresses (for
>> obex over IP). IrDA doesn't need addressing since it's line-of-sight.
>>     
>
> Solid already does the enumeration (through bluez). As Solid is KDE's
> interface to the hardware, I thought we also need to go through Solid
> for OBEX; is it not the case?
> g
>
>   
For the kioslave we just need to use the obex-data-server
(http://wiki.muiline.com/obex-data-server) which was a GSoC Project from
the bluez developers.
obex-data-server is already used in kdebluetooth4 to receive and send
files to remote devices, and works like a charm. Its a high level dbus
API for openOBEX.
It provides a session interface, where easy methods like 'browse remote
files' and many more are perfect to use them within the kioslave module.
I've already written a C++/Qt wrapper for the ObexSession(Send Files)
and Arjan Topolovec has written a wrapper for the
ObexServerSession(Receive Files), this is ready to be used for the
kioslave (the obexsession wrapper  http://tinyurl.com/7krev5 ).

Solid is just the extra layer to provide easy access to diffrent
hardware backends. Obex is nothing hardware relevant, so we do not need
to encapsulate that via solid.

We also do not use plain openObex, this we already did in KDE3 and
kdebluetooth3 times. The way we need to go is dbus and therefore just
have to use the wonderfull obex-data-server.

Tom


More information about the Kde-hardware-devel mailing list