cheers and hello,
i wist to know whast the problem with bluetooth, what king of help are needed?
maybe i, or something friend of me, could help!
cheers and hello,
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.
Thanks!
Tim
On Tuesday 01 February 2011 23:02:11 Timothy Pearson wrote:
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?
On Tuesday 01 February 2011 23:02:11 Timothy Pearson wrote:
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?
I don't know. My guess is that once kdebluetooth is fixed applications 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
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: According to one of the code contributors (Matthias), the project is dead:
"to keep it short: KMobileTools is dead and I have no more time to contribute to KDE at the moment. Even if you manage to compile KMobileTools for KDE 4.x, do not expect it to work. The best you could achieve is reading information from a simulated mobile phone.
I agree that an app like KMobileTools is missing in the KDE sector. If you take the time to find your way in the source code and resume work, I am sure many people would be very grateful :-) I can promise that working on KMobileTools is a lot of fun.
Best regards, Matthias"
But, you can grab the latest version at svn:// anonsvn.kde.org/home/kde/trunk/playground/pim/kmobiletools but its only for KDE4 branch
On Tue, Feb 1, 2011 at 3:43 PM, Timothy Pearson <kb9vqf@pearsoncomputing.net
wrote:
On Tuesday 01 February 2011 23:02:11 Timothy Pearson wrote:
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?
I don't know. My guess is that once kdebluetooth is fixed applications 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
On Wednesday 02 February 2011 00:19:40 PICCORO McKAY Lenz wrote:
But, you can grab the latest version at svn:// anonsvn.kde.org/home/kde/trunk/playground/pim/kmobiletools but its only for KDE4 branch
There is a version for KDE3 as well. We have it in KDE:KDE3 https://build.opensuse.org/package/show?package=kmobiletools&project=KDE...
I did not check if it works though because I have no bluetooth devices. In regards of user interface the latest version is very different from th old version which was in KDE:KDE3 for ages.
wel, i will chek taht so then.. thanks, in some days i revive post for test... i first build on normal kde3 3.5.9 so then i build on squeeze kde3 3.5.12 trinity..
On Tue, Feb 1, 2011 at 5:13 PM, Ilya Chernykh neptunia@mail.ru wrote:
On Wednesday 02 February 2011 00:19:40 PICCORO McKAY Lenz wrote:
But, you can grab the latest version at svn:// anonsvn.kde.org/home/kde/trunk/playground/pim/kmobiletools but its only
for
KDE4 branch
There is a version for KDE3 as well. We have it in KDE:KDE3
https://build.opensuse.org/package/show?package=kmobiletools&project=KDE...
I did not check if it works though because I have no bluetooth devices. In regards of user interface the latest version is very different from th old version which was in KDE:KDE3 for ages.
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
kde now cant' compile in my squeeze version, i have testing (currenly on january, exact copy of squeeze stable)
so maybe the change its to soon for swicht kde trinity lenny to olstable and stable repos sync?
the bluez work are too boring
On Tue, Feb 1, 2011 at 5:17 PM, PICCORO McKAY Lenz mckaygerhard@gmail.comwrote:
wel, i will chek taht so then.. thanks, in some days i revive post for test... i first build on normal kde3 3.5.9 so then i build on squeeze kde3 3.5.12 trinity..
On Tue, Feb 1, 2011 at 5:13 PM, Ilya Chernykh neptunia@mail.ru wrote:
On Wednesday 02 February 2011 00:19:40 PICCORO McKAY Lenz wrote:
But, you can grab the latest version at svn:// anonsvn.kde.org/home/kde/trunk/playground/pim/kmobiletools but its only
for
KDE4 branch
There is a version for KDE3 as well. We have it in KDE:KDE3
https://build.opensuse.org/package/show?package=kmobiletools&project=KDE...
I did not check if it works though because I have no bluetooth devices. In regards of user interface the latest version is very different from th old version which was in KDE:KDE3 for ages.
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
-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com Cofundador de Venenux; http://shutendouji.net creador de massenkoh linux.
On Tuesday 01 February 2011 23:13:45 Timothy Pearson wrote:
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?
I don't know. My guess is that once kdebluetooth is fixed applications 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.
In KDE:KDE3 kmobiletools does not depend on kdebluetooth. It builds well with the modern bluez. Kdebluetooth indeed requires older bluez.
-
Ilya Chernykh -
PICCORO McKAY Lenz -
Timothy Pearson