Skip to content
Snippets Groups Projects
  1. Jan 14, 2011
  2. Jan 12, 2011
  3. Jan 11, 2011
  4. Jan 08, 2011
  5. Jan 07, 2011
  6. Jan 05, 2011
  7. Jan 04, 2011
  8. Dec 23, 2010
  9. Dec 16, 2010
  10. Dec 13, 2010
  11. Dec 09, 2010
    • mnissler@chromium.org's avatar
      Sanitize PrefStore interface. · f2d1f610
      mnissler@chromium.org authored
      This reworks the PrefStore interface, specifically:
      
      - Split up the interface into PrefStore, which only provides reading functionality, and the derived PersistentPrefStore for the actual user pref store
      - Remove the hurt-me-plenty prefs() function from PrefStore, instead provide Get/Set/Remove operations
      - Remove special handling of default and user pref store from PrefValueStore and put it into PrefService
      - Pref change notification handling now almost exclusively handled through PrefValueStore
      - Adjust all consumers of these interfaces (but keep ConfigurationPolicyPrefStore untouched, that's up next on the list)
      
      BUG=64232
      TEST=existing unit tests
      
      Review URL: http://codereview.chromium.org/5646003
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@68736 0039d316-1c4b-4281-b951-d872f2087c98
      f2d1f610
  12. Dec 07, 2010
  13. Nov 30, 2010
  14. Nov 26, 2010
    • joi@chromium.org's avatar
      Use BRANDING settings for IE CEEE. Simplify chrome_dll_version handling. · f960aacc
      joi@chromium.org authored
      Adding new CEEE_PRODUCT_FULLNAME key to the BRANDING file. Adapting version.h.in to define a preprocessor constant for it. Using this and the other version/product name constants in IE CEEE's .rc files.
      
      Piggybacking on MAD's recent changes to make %NAME% a variable in the .rgs files to fairly easily get the product name from branding in there. Naming the toolband with the product name directly (as it is what shows up in IE's View/Toolbars menu), the BHO with an added "Helper" and the broker with an added "Broker".
      
      Removing the 'chrome_dll_version' target from chrome.gyp, and skipping code generation of chrome_dll_version.rc. Instead we have a source file with that name, that includes the verson.h generated by the 'chrome_version_header' target. This is cleaner and less code generation.
      
      Fixing 'chrome_dll_nacl64' target, it seemed like it wanted to have version information, but it didn't.
      
      Cleaning up the way sources are specified in several of the chrome_tests.gypi targets, to use fewer source! statements just to remove source files that are Windows-only (put them in the Windows-only section instead).
      
      BUG=none
      TEST=Visible change should be that user-visible names in Chromium builds are like "Chromium Extensions Execution Environment" (with "Broker" or "Helper" appended when appropriate), i.e. they lose the "Google" part.
      
      Review URL: http://codereview.chromium.org/5360002
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@67457 0039d316-1c4b-4281-b951-d872f2087c98
      f960aacc
  15. Nov 23, 2010
  16. Nov 12, 2010
  17. Nov 10, 2010
  18. Nov 09, 2010
    • gfeher@chromium.org's avatar
      Refactor: move all the policy-template related targets into one gypi file · acd5f4fb
      gfeher@chromium.org authored
      BUG=none
      TEST=build completes on all platforms
      
      Review URL: http://codereview.chromium.org/4644002
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65510 0039d316-1c4b-4281-b951-d872f2087c98
      acd5f4fb
    • apatrick@chromium.org's avatar
      - Relanding 61718. · e09cee46
      apatrick@chromium.org authored
      I disabled the GPU watchdog in three new cases:
      - If the OSMesa software renderer is in use. This will disable it on bots.
      - When running on valgrind, whether on a bot or locally.
      - In debug builds
      
      I added a GPU process initialization time to the GPU info.
      
      I moved the GPU initialization code outside the watchdog protection because it
      can take a long time and trigger the watchdog.
      
      I increased the timeout. I set up a field trial with different timeouts to see
      the rate of failure for each period.
      
      Original CL description:
      
      I added a watchdog thread that intermitently checks the main thread can respond
      to tasks posted on its message queue.
      
      I fixed some bugs that prevented GGL from failing when the GPU channel was
      lost.
      
      Added a command line swith to disable the watchdog thread for debugging
      purposes.
      
      TEST=try, local testing of all features
      BUG=none
      
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@65461 0039d316-1c4b-4281-b951-d872f2087c98
      e09cee46
  19. Nov 08, 2010
  20. Nov 04, 2010
  21. Nov 02, 2010
  22. Nov 01, 2010
  23. Oct 29, 2010
Loading