[chromium-dev] Re: Claimings
I have Linux plugins and a bottle of Jack. On Tue, Feb 10, 2009 at 4:16 PM, Avi Drissman wrote: > I have the TabContents.nib, and the Mac tab_contents_controller. > > Avi > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Claimings
I have the TabContents.nib, and the Mac tab_contents_controller. Avi --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Claimings
We're trying out a spreadsheet on the Linux side. http://spreadsheets.google.com/ccc?key=prV2wWigilGslQBvu76GpQQ On Mon, Feb 9, 2009 at 3:37 PM, John Grabowski wrote: > (We talked about a spreadsheet for this... anyone have a link?) > I'm following the chain from " on URL in browser" --> "tell renderer do > something". This currently ends at tabs; I'm removing stubs (TabContents, > TabContentsDelegate, ...) and bringing in the real thing. > jrg > > On Mon, Feb 9, 2009 at 1:12 PM, Thomas Van Lenten > wrote: >> >> Follow up from the other week - >> >> I'm still digging into ProcessUtil::LaunchApp and the fall out from >> there. The current code in unittests and w/in chromium depends on a few >> things that windows offers since it gets handlers for this, the Mac & Linux >> world can't really map things like this, so we're going to end up needed a >> slightly beefer process object to provide some of what is needed (hopefully >> we'll be able to leave the unittests on the current api for now, the >> problems doesn't really cause the tests issues (or we've fixed them)). >> >> TVL >> >> >> > > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Claimings
I have a SimpleFontDataMac unfork in flight, plus windowless plugins (mostly Mac, but some overlap with Linux, especially header files) --Amanda --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Claimings
I had a tiny change that is snowballing again. I'll claim % git diff --stat trunk... chrome/browser/bookmarks/bookmark_model.cc | 30 +-- chrome/browser/bookmarks/bookmark_storage.cc | 29 +++--- chrome/browser/bookmarks/bookmark_storage.h|5 +- chrome/browser/browser.scons |3 - chrome/browser/browser_init.cc |1 + chrome/browser/history/expire_history_backend.h|3 +- chrome/browser/history/history.cc |5 + chrome/browser/history/history_backend.cc |2 +- chrome/browser/history/history_backend.h |3 +- chrome/browser/profile.cc |2 +- .../renderer_host/browser_render_process_host.cc |2 +- .../browser/search_engines/template_url_model.cc | 12 +-- chrome/browser/tab_contents/web_contents.h |1 + chrome/browser/visitedlink_master.cc |9 +-- chrome/browser/webdata/web_database.cc |2 +- chrome/common/chrome_constants.cc |3 +- chrome/common/chrome_constants.h |2 +- chrome/common/temp_scaffolding_stubs.cc| 98 chrome/common/temp_scaffolding_stubs.h | 79 chrome/test/testing_profile.cc | 12 +-- chrome/test/testing_profile.h |2 +- 21 files changed, 162 insertions(+), 143 deletions(-) On Mon, Feb 9, 2009 at 3:53 PM, Paul Godavari wrote: > I'm working on getting the ResourceDispatcherHost operational, starting with > its unittest. > Paul > > On Mon, Feb 9, 2009 at 3:41 PM, Jeremy Moskovich > wrote: >> >> I'm tightening up the IPC Channel tests and adding some Mac-specific >> ones... >> >>> >>> On Mon, Feb 9, 2009 at 3:37 PM, John Grabowski wrote: (We talked about a spreadsheet for this... anyone have a link?) I'm following the chain from " on URL in browser" --> "tell renderer do something". This currently ends at tabs; I'm removing stubs (TabContents, TabContentsDelegate, ...) and bringing in the real thing. jrg On Mon, Feb 9, 2009 at 1:12 PM, Thomas Van Lenten wrote: > > Follow up from the other week - > > I'm still digging into ProcessUtil::LaunchApp and the fall out from > there. The current code in unittests and w/in chromium depends on a few > things that windows offers since it gets handlers for this, the Mac & > Linux > world can't really map things like this, so we're going to end up needed a > slightly beefer process object to provide some of what is needed > (hopefully > we'll be able to leave the unittests on the current api for now, the > problems doesn't really cause the tests issues (or we've fixed them)). > > TVL > > > >>> >> >> >> > > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Claimings
I'm working on getting the ResourceDispatcherHost operational, starting with its unittest. Paul On Mon, Feb 9, 2009 at 3:41 PM, Jeremy Moskovich wrote: > I'm tightening up the IPC Channel tests and adding some Mac-specific > ones... > > >> On Mon, Feb 9, 2009 at 3:37 PM, John Grabowski wrote: >> >>> (We talked about a spreadsheet for this... anyone have a link?) >>> I'm following the chain from " on URL in browser" --> "tell renderer >>> do something". This currently ends at tabs; I'm removing stubs >>> (TabContents, TabContentsDelegate, ...) and bringing in the real thing. >>> >>> jrg >>> >>> On Mon, Feb 9, 2009 at 1:12 PM, Thomas Van Lenten >> > wrote: >>> Follow up from the other week - I'm still digging into ProcessUtil::LaunchApp and the fall out from there. The current code in unittests and w/in chromium depends on a few things that windows offers since it gets handlers for this, the Mac & Linux world can't really map things like this, so we're going to end up needed a slightly beefer process object to provide some of what is needed (hopefully we'll be able to leave the unittests on the current api for now, the problems doesn't really cause the tests issues (or we've fixed them)). TVL >>> >>> >>> >> > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Claimings
I'm tightening up the IPC Channel tests and adding some Mac-specific ones... > On Mon, Feb 9, 2009 at 3:37 PM, John Grabowski wrote: > >> (We talked about a spreadsheet for this... anyone have a link?) >> I'm following the chain from " on URL in browser" --> "tell renderer >> do something". This currently ends at tabs; I'm removing stubs >> (TabContents, TabContentsDelegate, ...) and bringing in the real thing. >> >> jrg >> >> On Mon, Feb 9, 2009 at 1:12 PM, Thomas Van Lenten >> wrote: >> >>> Follow up from the other week - >>> >>> I'm still digging into ProcessUtil::LaunchApp and the fall out from >>> there. The current code in unittests and w/in chromium depends on a few >>> things that windows offers since it gets handlers for this, the Mac & Linux >>> world can't really map things like this, so we're going to end up needed a >>> slightly beefer process object to provide some of what is needed (hopefully >>> we'll be able to leave the unittests on the current api for now, the >>> problems doesn't really cause the tests issues (or we've fixed them)). >>> >>> TVL >>> >>> >>> >>> >> >> >> >> > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Claimings
(We talked about a spreadsheet for this... anyone have a link?) I'm following the chain from " on URL in browser" --> "tell renderer do something". This currently ends at tabs; I'm removing stubs (TabContents, TabContentsDelegate, ...) and bringing in the real thing. jrg On Mon, Feb 9, 2009 at 1:12 PM, Thomas Van Lenten wrote: > Follow up from the other week - > > I'm still digging into ProcessUtil::LaunchApp and the fall out from there. > The current code in unittests and w/in chromium depends on a few things that > windows offers since it gets handlers for this, the Mac & Linux world can't > really map things like this, so we're going to end up needed a slightly > beefer process object to provide some of what is needed (hopefully we'll be > able to leave the unittests on the current api for now, the problems doesn't > really cause the tests issues (or we've fixed them)). > > TVL > > > > > --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
