[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 125458] Improve KIOSLAVES for non-KDE apps
From:       Thiago Macieira <thiago () kde ! org>
Date:       2006-04-18 1:28:28
Message-ID: 20060418012828.18766.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=125458         




------- Additional Comments From thiago kde org  2006-04-18 03:28 -------
Because of general incompatibilities. For instance, propagating the information that \
the source was read-only is difficult.

If you open an HTTP file on a non-KDE application, you'll get a local temporary file, \
which the application may decide to write to (even if we make it read-only). Then KIO \
cannot upload it to the server and we have no easy way of telling the user of that.

At the same time, users may be already expecting that opening a remote file creates a \
local copy, so they save to the temporary file. They would be surprised if suddenly \
the remote copy started to be modified.

Finally, saving in the background may not be a good idea. In a normal KDE \
application, saving to a remote file may be a slow operation and the user will get a \
progress dialog blocking the UI while the operation is happening. There's no way to \
do that in a non-KDE application, which means that the user doesn't get feedback for \
the operation.

So, in a few words, if apps want to get the full power of KIO, they should link to \
libkio.


[prev in list] [next in list] [prev in thread] [next in thread]