ok, lest see.
looking for that u said, its a horrorific work, easy, but stubwork, i hav' see some work like in ubuntu mixed kde3 with recent releases.. i try to made that work in the next week, no waranty ^_^u "sape"
in kmobiletools, project hav some time work only in svn brand, and no oficial stable releases are on.. its more dificult for non-powered developers:
> On Tuesday 01 February 2011 23:02:11 Timothy Pearson wrote:I don't know. My guess is that once kdebluetooth is fixed applications
>
>> > i wist to know whast the problem with bluetooth, what king of help are
>> > needed?
>> >
>> > maybe i, or something friend of me, could help!
>>
>> The bluez API changed. Someone would need to get into the Trinity
>> source
>> code and change the old bluez API calls to match the new API instead.
>>
>> It should be a relatively simple task, just somewhat time consuming.
>>
>> Let me know if you are still interested and I will point out the source
>> code that needs to be changed.
>
> This is only regarding kdebluetooth but what about kmobiletools?
>
that depended on it (such as kmobiletools) can be reactivated. I am not
confident on this however, not having looked at the source code myself.
Tim
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting