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

[Urs Wolfer]

On Tuesday 06 October 2009 07:27:32 Michael Howell wrote:
> 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.

+1 from me as well. Makes sense to me.

Bye
urs