Re: Re: [Bulk] [trinity-devel] Re: kbluetooth

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Michele Calgaro wrote:

> Hi Emanoil,
> I have no clue either.
> I see two possible ways to proceed:
> 1) have conditional compilation as discussed previously
> 2) have two different version of tdebluetooth, one for bluez5 and one for
> bluez4. Both have advantages and disadvantages.
> As far as I am concerned you have the freedom to choose the way you think
> is better/easier. Cheers
> Michele

Hi Michele,
yes indeed these are the two options.

1) it would make sense if code/system would be maintained in the future.
Given the all changes done KDE -> TDE, Qt -> TQt, dbus, bluez ... it would
be the hell of conditionals in the code

This is why  I tend to go for option 2.
In case of wheezy/bluez4 it would mean to port from KDE -> TDE (with some
minor updates/corrections)
For the rest/bluez5 the code needs to be changed to implement the bluez5
interface

I'm just asking, so that I know how you see it

thanks



---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx
For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting




[Index of Archives]     [Trinity Users]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [KDE]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux