
kfile_torrent
Source (link to git-repo or to original if based on someone elses unmodified work):
NOTE: This library is now in KDE CVS, and will be included with KDE 3.4. There will be no future updates to this entry. Remember that you can keep track of KDE development with KDE CVS Digest.
See also: http://www.bitconjurer.org/BitTorrent/
The Gentoo ebuild collection includes ebuilds for all the released versions. See the homepage for information on how to use it.
2004-05-22: The x86 Debian package is for v0.6, and was kindly sent in by Kharkoma. I'm providing it here for any Debian users who won't/can't install from source.
29-Aug-2004: No code changes, but I've fixed the Debian package link. I can be such a moron sometimes. =D
0.6: The code has been more Qt and KDE-ified. It should now compile for more compilers, and maybe even fix a few bugs, who knows. No new features though.
0.5: Added the functionality to edit the comment and default name of the torrent.
0.3: Initial release. Allows previewing of most of the interesting information that a .torrent holds. Doesn't show the individual file names; I don't know how to properly do that as a KFilePlugin.
Ratings & Comments
7 Comments
Someone needs to fix the weblinks. No links are working as of 1/7/05.
That's a neat little addition. I love it. The link to the debian package is broken (points to localhost). Debian users who want a system-wide installation should use ./configure --libdir=/usr/lib/ --datadir=/usr/share/
i like it a lot! there should be definetely more support for bittorrent in KDE. I dream of bittorent download handling in KGet. Ohhh, It would be great!
Hmmm, why not implement BitTorrent as a Kioslave? In that way, downloading from bittorrent would be no different from downloading anything else...And I believe kget would support it without any changes, am I correct?
KGet ought to do it, yes, if it's implemented as a kio slave... This might be a good place to start :) (it's even c++ ;) ) http://libtorrent.sourceforge.net/manual.html#simple-client
While im not able to do that myself, it makes a lot of sense to implement it that way. Though i doubt Kget would understand it, since its a 2 way protocol while kget normally deals with 1 way.. ( incoming ) But yes, i would also love to see this, BT is a pain in the butt on *nix..
I get this during make: /bin/sh ../libtool --silent --mode=compile --tag=CXX g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/kde -I/usr/include/qt3 -I/usr/X11R6/include -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -c -o bint.lo `test -f 'bint.cpp' || echo './'`bint.cpp bint.cpp: In member function `void BInt::init(ByteTape&)': bint.cpp:63: error: `memcpy' undeclared in namespace `std' bint.cpp: In member function `virtual bool BInt::writeToDevice(QIODevice&)': bint.cpp:93: warning: comparison between signed and unsigned integer expressions could tell me how to fix it? :) thanx in advance