Review request: QBluez

[David Rosca]

> Using Q* is usually frowned upon since the Qt people have made it quick clear
> that they reserve the right to use Q* names themselves, i'd look for a new
> name.

I see. What about renaming it to BluezQt?

> Also tried to run the tests and qbluez-managertest seems to get stuck forever.
> Does it take much to run? Does it need that i actually have bluetooth
> hardware?

Tests are running with both real org.bluez (system bus) and fake
org.qbluez.bluez (session bus). You don't need to have any bluetooth hardware,
nor Bluez installed at all to run the tests.

The reason why it hangs is probably that fakebluez cannot, for some
reason, start.
I have pushed a change that fixes the hang, and also show some info why it
cannot start.
Can you please send me the output of qbluez-managertest?

Thanks,
David

On Mon, Feb 16, 2015 at 11:51 PM, Albert Astals Cid <aacid at kde.org> wrote:
> El Dilluns, 16 de febrer de 2015, a les 10:40:44, David Rosca va escriure:
>> Hi all,
>> I'd like to ask for a review of the QBluez library [1].
>
> Using Q* is usually frowned upon since the Qt people have made it quick clear
> that they reserve the right to use Q* names themselves, i'd look for a new
> name.
>
> Also tried to run the tests and qbluez-managertest seems to get stuck forever.
> Does it take much to run? Does it need that i actually have bluetooth
> hardware?
>
> Cheers,
>   Albert
>
>>
>> QBluez is a Qt 5 wrapper for Bluez 5 DBus API.
>> I have started working on it as a GSoC 2014 project.
>> It is intended to be a libbluedevil replacement, main
>> difference being that every DBus call is made asynchronous.
>> It also exposes more Bluez API than libbluedevil, including
>> Obex API.
>>
>> This library will be used in Bluedevil frameworks branch.
>> I have also written a new Bluetooth plasmoid [2] that uses
>> a QBluez QML plugin.
>>
>> Bellow is a list of some additional QBluez features compared
>> to libbluedevil:
>>
>>  * it is a tier 1 framework
>>
>>  * asynchronous API using jobs/pending calls with possibility
>>    to run synchronously (for tests/cli apps)
>>
>>  * extended API - this currently includes API for Obex File
>>    Transfer, Obex Object Push and Profile API for implementing
>>    Bluetooth profiles
>>
>>  * build-time optional QML plugin - currently exposing Manager,
>>    Adapter, Device, DevicesModel and PendingCall
>>
>>  * possibility to be notified when method call finishes
>>    and to be notified about possible errors
>>
>> Currently, there is a qbluez branch in Bluedevil [3]. It will
>> be merged to frameworks branch once QBluez is reviewed.
>>
>> You can find generated documentation here [4].
>>
>> Thanks,
>> David Rosca
>>
>> [1] http://quickgit.kde.org/?p=scratch%2Fdrosca%2Fqbluez.git
>> [2] https://github.com/nowrep/qbluez-plasmoid
>> [3]
>> https://projects.kde.org/projects/kde/workspace/bluedevil/repository/show?r
>> ev=qbluez [4] http://david.rosca.cz/qbluez-apidoc/html/
>> _______________________________________________
>> Kde-frameworks-devel mailing list
>> Kde-frameworks-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>