Re: Webkit-gtk and MacOSX

Am Wed, 26 Aug 2009 10:45:00 +1000
schrieb Davyd Madeley <davyd madeley id au>:

> On Tue, 2009-08-25 at 21:44 +0200, Kristian Rietveld wrote:
> > On Tue, Aug 25, 2009 at 9:35 PM, Xan Lopez<xan gnome org> wrote:
> > > WebKit is the native layer on top of WebCore offered by each port
> > > for their platform, so the answer to that is: yes, WebKitGTK
> > > provides GObject APIs which are all "specific" to it.
> > 
> > Right, so another question: does the GObject API contain stuff that
> > is not possible in the native layers for other platforms?
> Surely you'll want the GObject API for programming in your
> GObject-based toolkit. Otherwise you're effectively using a different
> widget and kill your portability.
> So surely the solution is WebKit-GTK+ on top of a system WebCore. I
> guess what would be attractive is to take the other existing system
> components used by WebKit on MacOSX and use those where possible too.

WebCore has no stable API and no public symbols, it is built
statically. As soon as the framework is upgraded it would break.

Further more WebKitGTK exposes libsoup to the API, so things like proxy
server or HTTP cookies can be accessed. This would break completely
since the Mac WebKit doesn't use this.

As an exception JavaScriptCore is identical in features in all ports of
WebKit. If anything, you could look into making that work independent
from the rest of the framework.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]