what separate core(libktorrent?) and GUI? Like gaim and libgaim(libpurple)..

Then is possible perhaps create non-X11 bittorent client, with features of ktorrent

0K!AS

Sorry, my english is very bad.

lucke wrote:You could simply write some small script that checks whether xscreensaver (or whatever) is active and sets ktorrent's max download/upload limit via dcop (dbus in the future).

Aha! How about a script manager, like Amarok's? Makes it easier to install and run scripts, almost plugin-like. I can think of at least a couple of candidates for these kinds of scripts (the abovementioned, status message in kopete with current up/down;), automatically fetch/load torrents, etc.).
Maybe borrow some code from Amarok (open source is goood).

Guffen

Perhaps KTorrent will be able to take advantage of the goodness of KDE4's Kross (scripting framework).

lucke wrote:Perhaps KTorrent will be able to take advantage of the goodness of KDE4's Kross (scripting framework).

I'm already planning to add kross support.

Hi I just wanted to say that in the lastest ktorrent 2.2 in feisty (thanks to backports) the .mkv is working fine now thanks a lot. I like this release, just discovered the web plugin interface and it has become a must for me, and ktorrent is now even less cpu demanding, great.

Don't know if this has been said, but I'd like something like dynamic or "smart" groups. Now I have like 20 uploads and 4 downloads running, making a group with "torrents downloaded within the last 24 hours" would be nice.

kaminix wrote:Don't know if this has been said, but I'd like something like dynamic or "smart" groups. Now I have like 20 uploads and 4 downloads running, making a group with "torrents downloaded within the last 24 hours" would be nice.

You could sort by time and select the ones you need but that might just be a pain. I agree it would be a nice feature, define groups by certain values - ratio, status, % done, download/seed time, and time left would be a few of my choices. Maybe a panel opens up for custom group definition.

btharper1221 wrote:

kaminix wrote:Don't know if this has been said, but I'd like something like dynamic or "smart" groups. Now I have like 20 uploads and 4 downloads running, making a group with "torrents downloaded within the last 24 hours" would be nice.

You could sort by time and select the ones you need but that might just be a pain. I agree it would be a nice feature, define groups by certain values - ratio, status, % done, download/seed time, and time left would be a few of my choices. Maybe a panel opens up for custom group definition.

Yeah, realised that when writing. But as you said, still a nice idea.

EDIT: Also a sort-by-tracker would be nice. Both as tabs and columns. And possibly an option to make aliases for the trackers you use the most.

Hello,

I started using Ktorrent short time ago (via Fink on OSX PPC), and I would like to make some suggestions for new features that came up to my mind. I'm using µtorrent on XP and Azureus on Suse too, therefore I will focus on issues from a "switchers" perspective.
I needed some time (and reading in this forum) to figure out how trackers are handled in torrents with multiple trackers given (correct me if I'm wrong):

- Only one selected tracker is used, all other trackers are neglected

I read an earlier post that this behaviour is intentional. Nevertheless this is inferior to the handling by µtorrent and Azureus, both announcing to every tracker given in the torrent. Quite often trackers on one torrent differ on the peers beeing active (f.e. check out Isohunt or btjunkie, they state for every tracker in a torrent data about the number of seeders and leechers beeing active). Therefore one needs to manually switch between the different trackers. Shure, DHT and PX could lessen the effect of this behaviour, but neither all clients support them, nor are they activated in every client.

- While it is possible to add trackers to a torrent manually, it is impossible to delete trackers specified initially in the torrent file.

Either µtorrent and Azureus allow the user to delete trackers from the torrent, even if specified in the torrent file. This is usefull in the following cases:
The tracker is down/dead
The tracker has reached is capacity, denying new connections ("peer limit reached").

Hence I request a updated "tracker handling" for multi-tracker torrents, which should result in Ktorrent

- announcing to every tracker specified in the torrent file (without user interaction necessary, obeying to the intervals set by the trackers)
- allowing the user to delete trackers specified in the torrent file manually

Otherwise, I'm rather content with Ktorrent and it's features (that's why I put up with the hazzle of running a KDE application on OSX).

Keep up the good work