More specific KIO Error Strings

Aaron J. Seigo aseigo at
Mon Mar 31 03:44:55 BST 2008

On Sunday 30 March 2008, nf2 wrote:
> At the moment the KIO error messages are limited to the pre-definded
> messages in KIO::buildErrorString(int errorCode, const QString
> &errorText). The errorText doesen't contain a full description of the
> problem, but rather the host-name or file-name to be inserted into the
> pre-definded messages. I wonder if it would make sense to allow slaves
> to construct error messages themselves.

probably not. it's just asking for more work for the slave owners and more 
inconsistencies (not to mention more strings for translation).

> This would be particularly 
> useful when porting KIO to VFS-systems which already provide such full
> (and translated) error messages.

of course, the messages in KIO are also translated already.

> My proposal would be that KIO::buildErrorString() just returns the
> errorText when it is prefixed with something like "{vendor} ".

that would be a horrible, horrible hack. yes, it preserves the current API but 
magic strings in parameters that change how things work is .. not very 

> That way we could also communicate the identity of the actual VFS-system
> vendor.

why does it matter to the user what the identity of the actual VFS vendor is?
what are your exact use cases? 
(evidently i'm missing something here, because i don't see the point =)

Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the kde-core-devel mailing list