[WebKit-devel] KDE Webkit status update...

[Michael Howell]

On Monday 05 October 2009 21:37:24 Dawit A. wrote:
> If you look at it from that point of view you when creating an API you
>  would realize that what is needed for QtWebKit/KDE integration is
>  re-implementation of the bulding block Qt classes such that all
>  applications/kparts, without exception, benefit equally. How do we do that
>  ? Why we follow the precedence set by KIO::AccessMananger. For example, I
>  am doing the same thing for the cookiejar integration right now. I am
>  going to offer a wrapper class for inclusing in KIO or other appropriate
>  location (e.g. wherever kdewebkit is going to go). Once that is done, all
>  a developer has to do is simply create an instance of these classes and
>  set them in the generic or own versions of the QWebView/QWebPage versions
>  and viola KDE integration. Everything else to me is application/part or
>  whatever specific and needs to be implement there.
Make sense.

-- 
Please don't send HTML-only mail (if you like, you can use multipart). If you 
forward messages, please clean off the garbage. Thanks! 
Michael Howell 
mhowell123 at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/webkit-devel/attachments/20091005/9cf4f6f0/attachment.sig