Some of you may have observed (perhaps with much amusement!) my
various efforts to get a functioning build of WebKit that could be
used without CFNetwork, CoreGraphics, and other Apple-only libraries.
Things are working well, and I would like to try to come up with a
design for a proper interface for clients of the Cairo-based WebKit.
Ideally, this effort would be nearly identical to the Safari
WebKit.dll. Certainly, virtually any service that WebKit.dll might
be providing to the Safari executable will be similarly useful to
other client software. In fact, the only real problem with the WebKit
interface in its current form is that there are several CFNetwork-
specific data types (e.g., CFURLRequest, CFHTTPCookieStorageRef, and
so forth).
Right now, I have been peppering portions of WebKit with #ifdef's,
leaving various things implemented as "E_FAIL" and so forth. This has
not been incorporated into WebKit proper, since this flies in the face
of the preferred design goals of the project. However, it seems silly
to add a half dozen files for the non-Apple port containing a series
of E_FAIL declarations.
I wanted to see if anyone had suggestions for a preferable way to
address this problem, so that I can work on getting this last group of
changes incorporated in WebKit proper for general use.
Best regards,
-Brent
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
