I'm going to try and use the WebKit source to make it do what I need
it to do.
That's a bad idea, unless you like rewriting your code for
(potentially) every OS update, having a large test matrix that allows
you to test against multiple "dot releases" (and various "security
updates", not to mention potential Safari public betas, etc...),
refactor your code to be able to support multiple SPI/code paths (such
as by having all that code factored off into a loadable bundle which
is loaded based on WebKit version), and dealing with customers that
complain that your app stops works correctly "for no reason" (other
than the fact that they applied a security update). After all, WebKit
is probably updated more than any other single OS component...
Just because the source for WebKit is available does not make any of
those private APIs public.
Glenn Andreas email@hidden
The most merciful thing in the world ... is the inability of the human
mind to correlate all its contents - HPL
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
