From kde-devel Sat Dec 30 17:11:55 2000 From: martijnklingens () netscape ! net Date: Sat, 30 Dec 2000 17:11:55 +0000 To: kde-devel Subject: Bug#17877: Editing documents opened from Konqueror from non-local storage doesn't work correctly X-MARC-Message: https://marc.info/?l=kde-devel&m=97819681332331 Package: kdelibs Version: KDE 2.1 Beta 1 Severity: normal Installed from: SuSE 7.0 RPMs Before I describe my bug below: I know that this is actually a wishlist item, but novice users that are not familiar with KDE's or Linux's architecture will recognize this as a bug and not as a missing feature. Therefore, I'm filing this bug from a user's point of view, and not a developer's. Whenever I open a document from a non-local location like an ftp link to my other computer I cannot save a file until I close the application. When I close, the kfmclient asks me if I want to resync the file, but saving a file from the application does not work correctly. This is obvious behaviour for legacy X applications that don't know KIO, but e.g. kedit should be able to handle kio urls natively. This behaviour raises a few issues and questions. I think the best approach would be to add a checkbox in the keditfiletype database whether an application is kio compatible or not. If so, the application is started with the original url and not from kfmclient's local cache. Legacy X apps will still be started from kfmclient. In this case, however, it would be wise to tell users that changes will not be applied until you close the application. A checkbox to turn that warning off is welcome there. Another option, which is more difficult to implement in a user friendly way is to define addresses that should always be opened using kfmclient, because they are behind a dialup link. That would make it possible for me to edit files on the internet offline, without having to keep the line open, but still allows me to access other files on my LAN directly. The problem with this option is that even if you normally want to use offline editing, there may be cases in which you still want to force an application to use kio. An example would be editing a remote web site when you want to be able to preview the results directly. Whatever approach is used (this or another solution), I am willing to help with it, _BUT_ I don't have a permanent internet connection and virtually no knowledge of KDE/Qt programming, so I'm not sure if it is a good idea if I do. After typing this long piece of text, I'm wondering if the mailing list isn't a better place for this. I'm leaving it up to you to decide, but apologies if this indeed is a mailing list issue (I'm not subscribed to them) Thanks in advance for working these issues out. Feel free to send me an email if you have more questions, or want to discuss this issue any more. Martijn Klingens (submitted via bugs.kde.org) >> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<