I said this back when we set up the Chromium project before launching the public beta. We deliberately decided not to change any of the code (see all our include lines that start with CHROME_ or chrome/ etc.)
There should be no difficulty or careful judgment to be made here. It's very simple. "In code, it's chrome." The emphasis is always on consistency in google coding style. It seems any time a legal department is involved in something the failplane takes off -_-. -Ben On Wed, Apr 29, 2009 at 2:04 PM, Evan Martin <[email protected]> wrote: > > On Wed, Apr 29, 2009 at 1:51 PM, Ben Goodger (Google) <[email protected]> > wrote: >> I'll raise this again: >> >> your js object that methods hang off should be called "chrome" not >> "chromium"... we use "chrome" in all of our other API points >> (chrome-ui:// and chrome-extensions:// protocol schemes, the user >> agent string etc). >> >> FYI - Chromium is the name of the project, not the product, and should >> never appear in code. I should probably add this to the style guide on >> dev.chromium.org! > > It might be worth bringing this up as a top-level thread, as it's news to me. > Not that I disagree, but grepping for "chromium" in the code indicates > it might be a surprise to others. > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
