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

[Andrea Diamantini]

On Tuesday 06 October 2009 06:37:24 Dawit A. wrote:
> On Monday 05 October 2009 22:51:49 Michael Howell wrote:
> > On Monday 05 October 2009 09:15:58 Dawit A. wrote:
> > > On Sunday 04 October 2009 11:05:48 Urs Wolfer wrote:
> > > > I just have found another issue we need to think about:
> > > > kdewebkit/settings/webkitsettings.h is not a public header, but used
> > > > by the part. This is a no-go. Either we need to cleanup this header
> > > > and install it, or remove the direct ussage of this class. I prefer
> > > > #2.
> > >
> > > Almost all of the WebSettings class deals with configuration that is
> > >  specific to Konqueror and hence should be moved to webkitpart as well.
> > > The two uses of WebKitSettings I personally added for determining
> > > whether or not the cookiejar is enabled can easily be replaced with
> > > public get/set member functions in KWebPage and the one that computes
> > > font sizes can trivially be relocated to webkitpart where it actually
> > > belongs...
> >
> > How are font defaults, JavaScript defaults, and such specific to
> > Konqueror? KHTMLWidget gets those settings outside Konqueror. If your app
> > needs them overridden (embedded WebKit using JavaScript), you can
> > override them.
> 
> I actually meant khtmlpart not Konqueror. That is a mistake on my part. As
> such these configurations should be either part of the webkitpart or
>  offered as a public API as demonstrated by the problem Urs mentioned
>  above.
> 
> Let me throw back the same question at you. Why would a completely distinct
> and spearate web rendering engine need to read the settings and
>  configuration of a completely different engine unless it wants to provide
>  the same consistent look and feel when used in existing applications
>  (which 99% of the time is Konqueror) ? Do all applications that use
>  QtWebKit, but want to integrate with KDE technology want to use these
>  khtml specific settings ? I somehow doubt that is the case... I just do
>  not see why a browser like rekonq that uses QtWebKit, but want to provide
>  KDE integration, want do that.

+1 (obviously) from here :)

I'd just let you know that after rekonq 0.3 release (I hope it will happen in 
one month) I'll push rekonq development into integration with kdewebkit.

I hope rekonq will be a good test case for a generic kde webkit API.

Regards,
-- 
Andrea Diamantini, adjam
GPG Fingerprint: 57DE 8E32 7D1A 0E16 AA52 59D8 84F9 3ECD DBF9 730F

rekonq project
WEB: http://rekonq.sourceforge.net
IRC: rekonq at freenode