Version: (using KDE KDE 3.4.3) Installed from: Fedora RPMs OS: Linux Please, write your own FTP client code (or use code of some CLI FTP client). Using kioslave causes Krusader to be a very bad FTP client. It's clumsy, problems with password saving,...
If you have troubles with kioslaves, report bugs against them, not against applications that are using them.
it is not about kioslaves' bugs. it is about principle of using kioslaves within krusader. this design causes krusader not to be a good FTP client. that's why i'm writing to krusaders' bugzilla. this is not a bug report, this is a wish. throw away your vanity, guys.
+1
Can you give specific examples of why using ioslaves in general is a bad design decision for Krusader? Since you said it's not about kioslave bugs, I can only assume it's something with how KIO works in general. But I fail completely to see your reasoning. All I see are some colourful messages about vanity, clumsiness, "it's bad", etc.
For example, you can't disconnect manually from an ftp connection. Or can you?
- it is slower than FTP software with built-in client - it sends login info every time you do 'cd', doesn't it? - no disconnect
Yes, there's no disconnect option, but that can be added to kio_ftp. No, it does not reconnect at every login. But it may have to if it disconnected due to timeouts. No, it's not slower.
Of course, I meant "no, it does not reconnect at every 'cd'"
- there is no viewable log - when I do a file transfer and wait until it is finished and then enter a different directory, it creates a new connection (because the one used for file transfer isn't probably ready or what) - it sometimes causes crashes (when I cancel some re-login operation and so on) - hard to reproduce when needed
Ok, thanks for the feedback. It's appreciated. I'd like to recommend you open wishlist entries for kio/ftp here in bugs.kde.org for all of those features you'd like to see, just like your 1st item. Your second one actually is caused by the way KIO works today. So there's really no way around it, today. I'd like to revise that for KDE 4, however. So, yes, another wishlist entry (for kio/general now). As for the third, no, kio_ftp cannot do that. It's an external process, so it cannot crash krusader unless krusader itself or libkio has a bug. This in turn means you should file a bug report whenever it happens again for you so that we can fix it. In fact, this is an advantage: having an external process do your FTP means krusader is free from the hassle of implementing it again, dealing with network issues, etc. From where I stand, having a central FTP client code is an advantage. Besides, how many FTP clients understand per-site filename encodings? And how many of those read their config from kio_ftprc? (hint: you need one finger from one hand only to count) Other benefits: - code maintained by others - code quite well tested
Resolving as WONTFIX, currently we have one active developer creating new stuff and he's way too busy with real problems. As Thiago mentioned - using kio was important decision and I guess it won't change. Besides FTP looses importance these days. Side note: for long time you CAN disconnect (via Tools/Disconnect from net menu).