>> A situation has arisen (I improved the error messages for kio) where w=
e
>> need a queued detailedError message box. I am writing to get your stam=
p of
>> approval or comments.
>>
>> Originally I added a new queuedDetailedError() method - see patch.
>
>Looks ok. Added to CVS.

Ok.

>> btw. screenshots of the new error messages are here:
>>
>> http://yoyo.cc.monash.edu.au/~meddie/patches/errors/
>
>I think it is the wrong approach because it provides the user with
> suggestions and possible causes which are likely to be incorrect or
> irrelevant to a high degree.
>
>I think this falls into the category "The file does not exist or you do =
not
>have access to it.". This is your computer telling you that it has no id=
ea
>what the problem is but you are supposed to know? Instead it should tell=
 you
>"The file does not exist." or "You do not have permission to access to t=
his
>file." whichever is applicable. Along the same lines it shouldn't say "Y=
ou
>may have provided incorrect credentials" if you haven't provided cedenti=
als
>at all.
>
>I'm all for better error reporting but only if it is truly better. That
>requires domain knowledge and that is something that either the slaves
>themselves or the application itself has. But KIO has not.

I have been getting this feeling from a number of places now. I hindsight=
, I=20
really did rush this too much, and it's something I've been kicking mysel=
f=20
about *hangs head in shame*. I was just too enthusiastic for all the good=
 I=20
thought I was doing.

I would like to hide the new system away for kde 3.0; it's a simple chang=
e to=20
cvs. I realise that some i18n changes I made on Sunday (only a few, but t=
hey=20
were vital, things like the headings for the html page version) are unlik=
ely=20
to be picked up for a while too, which would not be ideal, so I would lik=
e to=20
revert those to (ie comment them out).

So, if there is no dissent, I will make the small changes to hide this aw=
ay=20
and to comment out the i18n strings I applied on Sunday so they don't=20
surprise translators when (if? I don't know much about it) the i18n=20
extraction happens again closer to the release... ok?

Then, when kde 3.1 opens up, I'll have another crack at it, with proper=20
consultation this time. I think the above difficulties can be solved by m=
ore=20
specific KIO::Error codes. The example above would be fixed by documentin=
g=20
the error codes to specify that the error_login_failed should be used any=
=20
time that authentication details are truly incorrect, that way KIO can ge=
t=20
the message right. I think this was how they were intended in the first=20
place. Plus, Tim and I have been discussing the new ERR_SLAVE_DEFINED, an=
d I=20
think we can get slaves to pass all the info (error, detail, causes,=20
solutions) through an agreed format in the errorText variable.

Thanks ,

Hamish