[Kde-extra-gear] RFC: Replacing kdebluetooth with kdebluetooth-dbus-integration-branch

[Daniel Gollub]

Hi,

since few month there is a port/rewrite[2] of kdebluetooth[1] which makes use 
of the BlueZ DBUS Interface. The main goal of this branch was avoiding any 
linking against bluez-libs and support the latest features of the BlueZ DBUS 
Interface. Since bluez-utils provides a DBUS Interface there is an issue with
kdebluetooth and pairing Bluetooth devices. bluez-utils requires a application
which acts as "Passkey Agent" and register via DBUS to the bluez-utils
dameon (hcid). The Agent gets triggered if there is any pairing request.

Beside the Passkey Agent implementation the kdebluetooth-dbus-integration
got some other changes:

- libkbluetooth got rewritten and wraps the entire BlueZ DBUS API
- kbluetoothd got renamend to kbluetooth
- kbluetooth is now a simple tray icon application
- ... which acts as Passkey Agent and Authorization Agent
- kio_bluetooth and kio_sdp got ported to rewritten libkbluetooth
- kio_obex got replaced by kio_obex2 (from kmobiletools)
- kio_obex2 is based only on obexftp (NEW: libusb support!)
- kcm_btpaired ported to new libkbluetooth
- added a Bluetooth monitor (kbluemon)
- rewrite of kbluelock
- added a Bluetooth Input Device Wizard

The Input Wizard is based on the BlueZ input service. It's planned to 
implement even more BlueZ services - like: transfer (OBEX), audio, ...

This is only intended for KDE3, there is no plan to port this for KDE4.
Since this version rely on BlueZ only. For KDE4 it's planned to make use of
Solid and the Solid Bluetooth backends. Work for the Bluetooth Solid based
kdebluetooth implementation for KDE4 already started.

Is there any objections to replace kdebluetooth with the
kdebluetooth-dbus-integration branch?

[1] http://websvn.kde.org/trunk/extragear/pim/kdebluetooth/
[2] http://websvn.kde.org/branches/work/kdebluetooth-dbus-integration/

best regards,
Daniel