Hi Darin, On Tue, Dec 30, 2008 at 5:12 PM, Darin Adler <[email protected]> wrote: > The specific issue here is how to make headers that work for external > clients that are not part of WebKit. WebKit's internal > platform-configuration macros and platform-independence framework were not > designed for use in WebKit's external programming interface.
I see. This make sense. > Please take a look at my comments in > <https://bugs.webkit.org/show_bug.cgi?id=23027> for some more specifics. I'm not sure I understand what you mean in your comments -- these routines are most definitely used by clients like WinLauncher. As I wrote in my bug update: "To not follow the existing WebKit.dll API implies the creation of a whole parallel API structure for clients that happen to be using the non-CG version of WebKit.dll. I desperately want to avoid this!" Just to clarify: Are you simply suggesting that a separate set of header files be used for the API (one set for CoreGraphics users, another set for Cairo users), while the internals of the WebKit.dll makes use of the internal (platform-agnostic) WebCore/GraphicsContext primitives? Thanks, -Brent _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
