[Webkit-unassigned] [Bug 16885] Official API for raw/GL embedders
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Jan 15 15:59:37 PST 2008
http://bugs.webkit.org/show_bug.cgi?id=16885
alp at atoker.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
------- Comment #6 from alp at atoker.com 2008-01-15 15:59 PDT -------
(In reply to comment #5)
> As a final note, I'm taking a slightly Linux-centric (and GTK-centric)
> implementor's view, but ideally we'd like to support WebKit across OSX, Win32,
> Linux and as much as possible. The chances of this seem increased when the API
> is built merely upon glib+cairo without bringing GTK itself into the equation
> (esp. when GTK is just being sidestepped as a fakey translation layer) but I'm
> not deeply worried either way.
>
Replying to your last comment first (the other stuff looks well considered, I
look forward to reviewing your proposal).
As you noticed, the GTK+ port already does work headlessly without actually
using GTK+. It should be fairly straightforard to make build fixes to allow for
a GTK+-less build, but dropping GLib is less ideal since it would be equivalent
to developing a brand new port.
So, I recommend that you ship the product with GLib and develop an API that's
shared with the GTK+ port.
I can help make the necessary build system changes and code fixes to allow for
a GLib+Cairo-only build (without GTK+) once we're done designing and
implementing the API. This seems to provide portability without heavy
dependencies and lets us use the same WebKit project infrastructure. Does that
sound good?
--
Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list