Apollo's port of WebKit
On Mar 22, 2007, at 9:38 AM, Chris Brichford wrote:
> I'll go with WebKit/apollo, WebCore/platform/apollo, and WebCore/
> bridge/apollo, unless I hear otherwise.
Please note: when we have some time for cleanup again the "bridge"
directory is
On Mar 22, 2007, at 9:38 AM, Chris Brichford wrote:
I'll go with WebKit/apollo, WebCore/platform/apollo, and WebCore/
bridge/apollo, unless I hear otherwise.
Please note: when we have some time for cleanup again the "bridge"
directory is supposed to go away. Every file currently in bridge
AM
To: WebKit Development
Subject: Re: [webkit-dev] Adobe Apollo's port of WebKit
Dear all
Unless some bad things happen between now and then, we will deliver our
"OWBAL" implementation of WebKit, as discussed previously in this
mailing-list. So the question of how to organize new WebKi
Dear all
Unless some bad things happen between now and then, we will deliver our
"OWBAL" implementation of WebKit, as discussed previously in this
mailing-list. So the question of how to organize new WebKit-based
products is highly interesting to me :-)
* Should we make our WebKit a subd
Here's my opinion. Others may disagree. :)
On Mar 21, 2007, at 2:34 PM, Chris Brichford wrote:
* What to call our sub-directory in WebCore/platform
I think "apollo" is appropriate. While I know it is just a code
name, it's very recognizable/familiar to people at this point.
* Should
Hi All,
Below is a document I have written up describing the WebKit port that
the Apollo team wants to build. We'd like to know what the community thinks of
the port we are proposing, what we should call such a port, and the process by
which we should start submitting patches to WebKit.
6 matches
Mail list logo
