The purpose of this document is to help organize and coordinate the effort to get a browser window up and running on Mac and Linux using as much of the code that is already there as possible (with temporary header and link scaffolding, plus ifdefs) as opposed to writing a bunch of throw-away code that duplicates what already exists on windows.The linux folks have already started working on 1-5. Since they are mainly based in SF, we figured the Mac folks in MtnView would be best suited to work with them and make sure everything was coming together on the Mac side (especially since Jeremy has already done a lot of work on the IPC refactoring).
Our goal is to get a double-clickable app with a working browser window using the real multi-process infrastructure (not TestShell) by mid-February. To that end, we put together a high-level list of things that need to be worked on.
Items 7-13are top-down and focused on creating a new platform browser window using the Browser model class. Pink has started stubbing out Browser/BrowserWindow as well as the Mac-specific Cocoa application controller (10). Work still needs to be done on Linux to get started on item 6, the main functions, which are currently building on Mac. Many of the larger supporting subsystems to main() and the browser window (profile, etc) are currently stubbed out (see chrome/common/temp_scaffolding_stubs.h/.cc) and can be worked on individually, in isolation.