[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: [Kde-extra-gear] RFC: Replacing kdebluetooth with
From: Kevin Krammer <kevin.krammer () gmx ! at>
Date: 2007-05-31 21:08:48
Message-ID: 200705312308.48879.kevin.krammer () gmx ! at
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
On Thursday 31 May 2007, Daniel Gollub wrote:
> 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.
As far as I understand without this it will not be possible to pair any new
devices, right?
> Beside the Passkey Agent implementation the kdebluetooth-dbus-integration
> got some other changes:
>
> - libkbluetooth got rewritten and wraps the entire BlueZ DBUS API
Must have been quite some work without using the Qt3 D-Bus bindings
Cheers,
Kevin
--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
[Attachment #5 (application/pgp-signature)]
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic