summaryrefslogtreecommitdiffstats
path: root/kio/kioexec/README
diff options
context:
space:
mode:
Diffstat (limited to 'kio/kioexec/README')
-rw-r--r--kio/kioexec/README26
1 files changed, 0 insertions, 26 deletions
diff --git a/kio/kioexec/README b/kio/kioexec/README
deleted file mode 100644
index daaa38bdb..000000000
--- a/kio/kioexec/README
+++ /dev/null
@@ -1,26 +0,0 @@
-kfmexec is launched when the user wants to open a remote file with
-an application that only supports local files.
-
-For this it does the following:
-- downloads a remote file to a temp location
-- starts a 'local' application with that temp file as argument
-- wait fors application to be exited
-- if the modification time of the file is different from the original one,
-(because the file was modified) then it offers re-uploading the modified version.
-This is how you offer network transparency to apps that don't have it.
-
-BUT: with KUniqueApplication, this breaks, because the app returns at once,
-so we have no way to know when the user finished editing the file...
-
-Conclusion: if the application has network transparency built-in, it should
-put "%u" in its desktop file - and kfmexec isn't used -. If it doesn't, either
-it's a TDEApplication and kfmexec does its job, or it's a KUniqueApplication
-and... kfmexec can't see modifications to the file. Be warned.
-
-From Waldo: "The program doesn't return _at once_. It returns
-after "newInstance()" returns. So if you open the file there it will still work.
-(Or rename it)"
-
-David Faure <faure@kde.org>
-20-May-2000
-