On Oct 3, 2008, at 9:17 PM, David Hyatt wrote:
After working for a while on the WebCore/platform/ directory, it's
become clear that people don't really know what this directory is
supposed to contain (and by people I mean pretty much everybody,
both inside and outside Apple). The
On Sat, Oct 4, 2008 at 12:27 AM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Oct 3, 2008, at 9:17 PM, David Hyatt wrote:
After working for a while on the WebCore/platform/ directory, it's
become clear that people don't really know what this directory is
supposed to contain (and by
This sounds good to me, although I'm not sure the files in platform/
need to move. I think the directory is fine under WebCore/ still.
dave
On Oct 4, 2008, at 2:56 AM, Eric Seidel wrote:
+1 for making wtf and platform their own projects/targets.
-eric
On Sat, Oct 4, 2008 at 12:27 AM,
On Oct 4, 2008, at 2:23 AM, David Hyatt wrote:
This sounds good to me, although I'm not sure the files in platform/
need to move. I think the directory is fine under WebCore/ still.
I could go either way, but I kind of like moving the platform
directory to a top level module because that
On Oct 4, 2008, at 12:27 AM, Maciej Stachowiak wrote:
We have a lot fewer layering problems with WebCore and WebKit in part
because they are separate modules, and you have to go out of your way
and make some Client interfaces to create unfortunate entanglements.
Some ports do have a problem
To answer my own question, if you link against WebCore, you have to
implement the functions in WebCoreLocalizedStrings from WebKit. That said,
you also have to implement loadResourceIntoBuffer in WebKitDLL. However,
there is this note from that function: //FIXME: We should consider moving
this to
6 matches
Mail list logo
