Qt Bluetooth in 5.5

[Jef Driesen]

On 19-03-15 20:10, Dirk Hohndel wrote:
> On Thu, Mar 19, 2015 at 03:23:28PM +0200, Lubomir I. Ivanov wrote:
>> On 18 March 2015 at 05:48, Dirk Hohndel <dirk at hohndel.org> wrote:
>>>
>>> Thiago,
>>>
>>> would Subsurface benefit from using Qt Bluetooth for our intended Bluetooth integration?
>>> This would cause some interesting architectural challenges with libdivecomputer (as that most definitely doesn’t want to depend on Qt), but I find it very intriguing that Qt now supports all of the platforms we are interested in… or am I missing something here?
>>>
>>
>> i can see that libDC has a parser API exposed, but i don't know if /
>> how does that works, but if Subsurface uses Qt's BT it can in theory
>> just use libDC as a parser (Thiago mentioned the same).
>>
>> i think it would be better for the student to first help Jeff get the
>> BT working in libDC for Win32 and Linux and then start working on the
>> Subsurface side.
>> but...if the OSX code is not going to be donated soon (or maintained
>> well in that aspect), i suggest we just use Qt's BT.
>
> My thinking was to have the student look at QtBt and figure out if that
> would be sufficient. If it is, then we'll use that and connect to the
> parser ourselves.
>
> Otherwise back to plan A :-)

It's certainly not my preferred option, but considering the time frame for a 
GSOC student, that might work as a temporary solution until the necessary 
libdivecomputer infrastructure is in place. At least we'll get some more 
experience with bluetooth that way. That alone is already worth something!

>> there is also the option for libDC to expose API to allow the libDC
>> user to specify the BT backend (e.g.. built-in VS external C-wrapped
>> Qt BT), but that's probably a ton of extra work for Jeff.
>
> Jef and I talked briefly about the options we have for BT. The last thing
> I want to do is to create a ton of extra work for him...

Well the changes that we need for bluetooth (see my other mail) are already on 
my todo list for other reasons. So this will have to be done anyway. But right 
now, I'm first working on *finally* getting v0.5 ready.

Jef