I'll go with WebKit/apollo, WebCore/platform/apollo, and WebCore/bridge/apollo, unless I hear otherwise.
Thanks for the feedback, Chris -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jean-Charles VERDIE Sent: Thursday, March 22, 2007 2:48 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 WebKit-based products is highly interesting to me :-) >> * Should we make our WebKit a subdirectory in WebKit like >> WebKit/COM? Should we make a new top level directory? > > I see two options here: > > (1) Fix the WebKit directory to have subdirectories for each > platform. That means all of the Mac subdirectories would move under > WebKit/mac. Then you could have WebKit/apollo. > (2) Have top-level directories for each WebKit, e.g., WebKitMac, > WebKitWin, WebKitApollo, WebKitQt, etc. > > My personal preference would be for (1), although note that Qt went > with (2) already. Other platforms can do (1) now without us having to > move our Mac files immediately, so that doesn't hold anything up. > (1) sounds really good and a clean approach of the multi-target issue, imo. Regards, -- Jean-Charles Verdié Pleyo, CTO mobile: +33 (0)6 282 616 05 skype: jcverdie _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-dev _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-dev
