14

Aim of KIO is to be transparent to aplications and offer unify way to access files in different places via different protocols.
Now this aim is fullfiled only partialy. KIOs works great for kde applications, but not for others. Gtk applications have problems especially with writing to KIOs, gimp has even problem with opening file from ftp using dolphin.

My solution is to mount all resources using fuse in some hidden directory, for egzamle ~/.kio and then return standard linux path for external applications. Kde applications would interpret the path as kio, whereas other applications would use standard linux path. There would be no problems with opening and saving documents because remote locations were being normaly mounted.

Gnome already have gvfs which works like that. Mayby there is a chance to standarize the way of accessing remote files

Like KIO Fuse?
http://techbase.kde.org/Projects/KioFuse

ivan wrote:Like KIO Fuse?
http://techbase.kde.org/Projects/KioFuse

Decided to approve this thread, so that OP can say if KIO fuse is enough.

ivan wrote:Like KIO Fuse?
http://techbase.kde.org/Projects/KioFuse

Yes, exactly. But it would be great to have this integrated in kde so all stuf could be mounted and unmounted transparently without using command prompt.

Notice that gvfs do the same work. It would be nice to standarize access to such mounted fuse filesystem, so nautilus as on your link would recognize fuse mounted by kio the same way as a fuse mounted by gvfs and show "tar://~/fuse-2.7.2.tar.gz/fuse-2.7.2/include" instead of "~/fuse-source/fuse-2.7.2/include" in the address bar.

It looks like gvfs will do this. It also looks like kio fuse is has not had any work done on it in a year.

Here's the link to bug report which I made some time ago, but it's not confirmed. If you approve my idea confirm that bug and vote:

https://bugs.kde.org/show_bug.cgi?id=185811