[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: KIOSlave errors an konqueror's handling of them
From:       David Faure <david () mandrakesoft ! com>
Date:       2002-01-25 14:42:23
[Download RAW message or body]

On Friday 25 January 2002 15:31, Hamish Rodda wrote:
> >>Well, that sounds great and is exactly the error:// stuff we were talking
> >>about on kde-cvs. If you think about it: how is Konqueror going to show
> >> that HTML in khtml? It can't just stick it in a temp file and open khtml
> >> on it, that would give a wrong URL in the location bar. Hence the idea of
> >> passing an error:// URL (something that doesn't exist yet) to khtml, 
which
> >> would generate the error message from that. Indeed, by passing the error
> >> code in the query, you can write nicely formatted error messages for each
> >> error code. If you feel like working on this, please do so, my todo list
> >> is growing much faster than I can empty it. Thanks ;)
> 
> Would it be ok to add a
> 
>   QString buildFancyErrorString(int errorCode, const QString &errorText);

I'd call it
buildHTMLErrorString() instead ;)
or just HTMLErrorString()

> method to global.cpp?  Then, global.cpp would load the i18n-ed error page 
from 
> the file system and pass it as a QString. This seems to me to make it a 
very, 
> very straightforward thing to do, technically speaking :)

Yup, but you also need to add support for error:// in khtml, and call it in 
KonqRun::handleError()  (as I see it)

> Then I have to write the pages... ;)
:)

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://people.mandrakesoft.com/~david, http://www.konqueror.org
KDE 3.0: Konquering the Desktops
[prev in list] [next in list] [prev in thread] [next in thread]