[Kde-hardware-devel] Bluetooth support in Solid

[Daniel Gollub]

On Thursday 22 March 2007 19:51:42 Daniel Gollub wrote:
> > Note that my ultimate goal is still to have the bluetooth devices appear
> > in the tree provided by Solid::DeviceManager. I'm fine with having a
> > separate set of classes for the pairing and the advanced bluetooth
> > operations, but once a device is paired it should be discoverable as any
> > other device (this way our applications would be able to find those
> > devices "for free" without doing some bluetooth voodoo in their code).

After "pairing" the input devices will appears in /sys/class/input/... and HAL 
will pick them up... so they find their way into the Solid::DeviceManager.
There is now a class called Solid::BluetoothInputManager and 
Solid::BluetoothInputDevice ... to manage and setup those "pairings" and 
connection with bluetooth input devices...

About bluetooth audio integration i am not quite sure anymore... how this will 
appear in the system. Have to take a deeper look in phonon... how this fits 
with the BlueZ Audio DBus API and A2DP...
http://bluetooth-alsa.sourceforge.net/

Maybe we should arrange a IRC meeting with some bluetooth audio devels and the 
phonon, solid devels...


>
> > - It would be ++cool to have also a fake bluetooth backend implementation
> > and a set of automated tests using it in order to test the frontend
> > classes.
>
> Is on my todo list as well ;)
>
There is now a "simple" fakebluetooth backend... and unit test for bluetooth 
frontend. I also implemented some basic features in solidshell to test...
unfortunately the solidshell doesn't work well with the fakebluetooth 
backend... the XML properties file gets only parsed when the constructor got 
called. How do you solve this problem with the other fakebackends? For me it 
seems they are lacking on the same problem...

> > Anyway, we should probably find a place in the subversion repository for
> > this code. Seeing the kdelibs subsystem freeze is close, those bluetooth
> > related classes will probably make it for 4.1 so we have some time to
> > make it mature. Of course the earlier we can start playing with it, the
> > better. ;-)
Well .. there still some days left until kdelibs freeze ;P
Most of the stuff is already done... so what about 4dotNULL?
Two people already contacted me, which want to write GUIs on top of the 
bluetooth solid implementation ... i don't want to disappoint them and let 
them wait until 4.1 :P 

*begging*

(The bluez backend build is broken... will adapt it later to the latest API 
changes... but it includes the solidshell changes...)
http://cryptomilch.de/~dgollub/KDE4/kdebase_solid_backend_bluez_20070326.diff
http://cryptomilch.de/~dgollub/KDE4/kdelibs_solid_bluetoothmanagment_20070326.diff


best regards,
Daniel