The K Desktop Environment

Next Previous Table of Contents

5. Questions and answers


Why should I use kget and not just kfm ?

If you use to download only one file at a time, kfm is probably enough for you ( if you do not need resuming ). KGet is utility for people who want to download many files and do not want to look at many progress dialogs.

KGet is independent from kfm. This means that when kfm dumps core ( though it doesn't happen too often since KDE 1.0 ), kget still works and transfers files.

KGetslave ( client process which is started for each transfer in kget ) is about 50 kilobytes smaller then kioslave in kfm, which is considerable, i.e. when you transfer 4 files at the same time. This is because I cut out stuff like tar and icon protocol, functions for moving files, listing and making directories etc., which are not needed for simple transfer of files.

However, kget is intended to closely cooperate with kfm as it uses KDE drag and drop. Use kfm to browse web and when you see something that you need - just drag it onto kget window and browse away. You do not have to remember the URL of the file anymore - kget will take care of it. And when kget can't connect - you can still leave transfer on the list and try to connect later.

Do you miss resuming in kfm ? KGet uses it.

Another thing is queueing. You can set number of transfers and then use kget as before. KGet will only start specified number of transfers, and keep others queued. Later, when first transfers finish, kget will start queued ones.

Next Previous Table of Contents