I have a copy of kdebluetooth-1.0_beta8.tar.bz2 for KDE3 as well as a copy of kmobiletools for KDE3.
I don't know how outdated these tools might be, be Trinity has no such tools. People around the world routinely sync mobile devices and cell phones with their computers. Trinity users have to use non Trinity apps to perform what is now a routine task for many.
Would we be wasting our time porting these apps to Trinity?
Darrell
I have a copy of kdebluetooth-1.0_beta8.tar.bz2 for KDE3 as well as a copy of kmobiletools for KDE3.
I don't know how outdated these tools might be, be Trinity has no such tools. People around the world routinely sync mobile devices and cell phones with their computers. Trinity users have to use non Trinity apps to perform what is now a routine task for many.
Would we be wasting our time porting these apps to Trinity?
Darrell
From what I can tell the KDE4 versions of these tools stink (not my wors, just google kdebluetooth! :-). *If* the KDE3 versions were halfway decent then yes, they should be brought into TDE.
Tim
From what I can tell the KDE4 versions of these tools stink (not my wors, just google kdebluetooth! :-). *If* the KDE3 versions were halfway decent then yes, they should be brought into TDE.
To my understanding, even after porting work will be needed to update to the latest bluez. Possibly for obexftp too. That might mean little more than fixing a few lines of code like we have done with libpng, ffmpeg, etc., or might mean a serious overhaul. I don't know.
Still, if we have some apps that can wrap around those tools and do things like device pairing and file syncing then we have a lot more than we do now.
Darrell
From what I can tell the KDE4 versions of these tools stink (not my wors, just google kdebluetooth! :-). *If* the KDE3 versions were halfway decent then yes, they should be brought into TDE.
To my understanding, even after porting work will be needed to update to the latest bluez. Possibly for obexftp too. That might mean little more than fixing a few lines of code like we have done with libpng, ffmpeg, etc., or might mean a serious overhaul. I don't know.
Still, if we have some apps that can wrap around those tools and do things like device pairing and file syncing then we have a lot more than we do now.
Darrell
Send me links to the latest versions and I'll throw a TDE-ported version of these two software packages into GIT (I have scripts here that handle the TDE conversion fairly quickly).
Tim
Le 24/11/2012 05:31, Timothy Pearson a écrit :
From what I can tell the KDE4 versions of these tools stink (not my wors, just google kdebluetooth! :-). *If* the KDE3 versions were halfway decent then yes, they should be brought into TDE.
To my understanding, even after porting work will be needed to update to the latest bluez. Possibly for obexftp too. That might mean little more than fixing a few lines of code like we have done with libpng, ffmpeg, etc., or might mean a serious overhaul. I don't know.
Still, if we have some apps that can wrap around those tools and do things like device pairing and file syncing then we have a lot more than we do now.
Darrell
Send me links to the latest versions and I'll throw a TDE-ported version of these two software packages into GIT (I have scripts here that handle the TDE conversion fairly quickly).
Tim
Hello, about kdebluetooth, I had already looked at it before. I've found that the last ubuntu package contained patches for 1.08 so I've used them. I also found and wrote other patches, so that it builds correctly against 3.5.13.1, even without TQT porting.
See here: http://git.trinitydesktop.org/cgit/tde-packaging/tree/redhat/extras/kdebluet...
Alas, as said Darell, it does not work with Bluez4 library, only Bluez3. So the application is useless, it does not detect any bluetooth receiver in the computer. I did not find any guide to easily port Bluez3 application to Bluez4.
Francois
Alas, as said Darell, it does not work with Bluez4 library, only Bluez3. So the application is useless, it does not detect any bluetooth receiver in the computer. I did not find any guide to easily port Bluez3 application to Bluez4.
This blog entry from a couple of years ago describes the problem:
http://blog.projectnibble.org/2010/08/08/how-ubuntus-broken-bluetooth-suppor...
In fairness, that blog entry indicates why bluetooth support in KDE4 has been problematic too.
In addition to the patch collection provided by Francois, this wiki provides some information about what might be needed to fix any ported kdebluetooth code:
http://wiki.openmoko.org/wiki/Manually_using_Bluetooth
Are there any bluez alternatives?
Seems other wrapper utilities are working with bluez 4, both GTK and KDE4. Perhaps we will need to study the code in some of those apps to port kdebluetooth to Trinity.
Darrell
Hello, about kdebluetooth, I had already looked at it before. I've found that the last ubuntu package contained patches for 1.08 so I've used them. I also found and wrote other patches, so that it builds correctly against 3.5.13.1, even without TQT porting.
See here: http://git.trinitydesktop.org/cgit/tde-packaging/tree/redhat/extras/kdebluet...
Alas, as said Darell, it does not work with Bluez4 library, only Bluez3. So the application is useless, it does not detect any bluetooth receiver in the computer. I did not find any guide to easily port Bluez3 application to Bluez4.
How well do tdepim kitchensync and gnokii work with cell phones?
Darrell
Send me links to the latest versions and I'll throw a TDE-ported version of these two software packages into GIT (I have scripts here that handle the TDE conversion fairly quickly).
http://humanreadable.nfshost.com/trinity/patches/kdebluetooth-1.0_beta8.tar....
http://humanreadable.nfshost.com/trinity/patches/kmobiletools-0.5.0-beta3.ta...
Darrell
-
Darrell Anderson -
Francois Andriot -
Timothy Pearson