Version: (using KDE KDE 3.2.1) Installed from: Unspecified When loading content via KIO, Quanta should check for the "davSource" metadata on the item. When present, it's a hint from a WebDAV server that the actual editable content is at the URL contained in this metadata (while the content at the current URL is a post-processed version of the text). This property is returned by some CMSs (e.g. Zope) to point the WebDAV-aware editors at the raw original document, rather than the document after it was integrated into the site's layout. Quanta, upon seeing the davSource metadata, should offer to get the davSource URL instead. The user should be able to mark "Always load source document" to avoid this dialog in the future (handy if you're constantly working with this CMS).
This would be an even better solution to the problem pointed out here: http://bugs.kde.org/show_bug.cgi?id=87769
To point out the importance: This functionality is part of the WEBDAV standard and should be implemented according to that. Every DAV-Server faces the same problem, this includes mod_dav on apache if you want to edit source files. Also this is part of the KIO moduleset which Quanta probably uses - but every other KDE product as well.
We agreed that the best solution is to provide a webdav+source and webdavs+source protocol, so the user can decided when he wants the source and when not and this not have to be implemented in each and every application.
Nice to finally see movement on this :-) But isn't "not the source" already covered by http/https so implementing yet another schema does not make sense? IMHO the decision "I want the source" is already done by choosing webdav/webdavs. Btw, who is "we" and how did you agree? Can you point to the thread in the mailinglist archive?
KDE 3 is no longer maintained. If his issue still persists in the latest version of KDE 4 (4.8 or higher), feel free to reopen this ticket.