summaryrefslogtreecommitdiffstats
path: root/cc/nine_patch_layer_unittest.cc
Commit message (Collapse)AuthorAgeFilesLines
* cc: Avoid expensive RenderingStats collection.danakj@chromium.org2013-02-021-7/+5
| | | | | | | | | | | | | | | When --enable-gpu-benchmarking is not present, don't do expensive steps in the benchmark collection (meaning don't call base::TimeTicks::Now()). BUG=170735 NOTRY=true Depends on: https://bugs.webkit.org/show_bug.cgi?id=108358 Review URL: https://chromiumcodereview.appspot.com/12095053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180224 0039d316-1c4b-4281-b951-d872f2087c98
* Avoid exposing gl bindings through cc public API headersjamesr@chromium.org2013-01-081-3/+4
| | | | | | | | | | | | | | | | | | The cc library uses chromium's gles2 bindings in third_party/khronos/... to bind to GL for rendering. However, users of cc may not be able to pull these headers in when including cc API - for instance, on mac any code that includes content/common/view_messages.h pulls in the Apple CGL api through npapi.h. On the 10.6 SDK these headers collide with chromium's gl headers. This avoids exposing gl2.h includes via layer_tree_host.h, mostly by not including prioritized_resource_manager.h directly in l_t_h.h. BUG=156175 Review URL: https://chromiumcodereview.appspot.com/11794019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@175554 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Finish the rename from cc::GraphicsContext to cc::OutputSurfacedanakj@chromium.org2012-12-061-4/+4
| | | | | | | | | | | | | | | It is far too confusing to deal with OutputSurface code when half the time it is called a GraphicsContext incorrectly. Cleaning this up so I can think about the code properly as I upstream the Ubercomp CL. R=jamesr,piman BUG=146080 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=171403 Review URL: https://codereview.chromium.org/11450019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171410 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 171403danakj@chromium.org2012-12-061-4/+4
| | | | | | | | | | | | | | | | | | | | | | cc_unittests is failing. Looks like something conflicted with this. > cc: Finish the rename from cc::GraphicsContext to cc::OutputSurface > > It is far too confusing to deal with OutputSurface code when half the time it is > called a GraphicsContext in correctly. Cleaning this up so I can think about the > code properly as I upstream the Ubercomp CL. > > NOTRY=true > R=jamesr,piman > BUG=146080 > > > Review URL: https://chromiumcodereview.appspot.com/11450019 TBR=danakj@chromium.org Review URL: https://codereview.chromium.org/11439026 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171406 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Finish the rename from cc::GraphicsContext to cc::OutputSurfacedanakj@chromium.org2012-12-061-4/+4
| | | | | | | | | | | | | | | It is far too confusing to deal with OutputSurface code when half the time it is called a GraphicsContext in correctly. Cleaning this up so I can think about the code properly as I upstream the Ubercomp CL. NOTRY=true R=jamesr,piman BUG=146080 Review URL: https://chromiumcodereview.appspot.com/11450019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171403 0039d316-1c4b-4281-b951-d872f2087c98
* Handle NinePatchLayer Resource Rebuilding.dtrainor@chromium.org2012-11-161-0/+12
| | | | | | | | | | | | | | | | When we minimize the application our PrioritizedResourceManager dies. This clears the PrioritizedTexture state and decouples the texture from the manager. When we bring our application back to the foreground a new PrioritizedResourceManager is created, but we still hold onto our old PrioritizedResource. Trying to reupload a bitmap on this resource fails due to a variety of DCHECK/CHECKs at this point. Now if the PrioritizedResource has no PrioritizedResourceManager we rebuild the resource. BUG=http://crbug.com/161278 Review URL: https://chromiumcodereview.appspot.com/11420021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168122 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Remove forbidden using namespace directives.tfarina@chromium.org2012-11-101-2/+3
| | | | | | | | | | | BUG=144576,144577 TEST=cc_unittests R=enne@chromium.org,jamesr@chromium.org,danakj@chromium.org Review URL: https://chromiumcodereview.appspot.com/11410022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167073 0039d316-1c4b-4281-b951-d872f2087c98
* Remove WTF and WebCore from cc/ and webkit/compositor_bindings/piman@chromium.org2012-11-101-2/+0
| | | | | | | | | | | Ding, dong... BUG=154451 Review URL: https://chromiumcodereview.appspot.com/11410021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@167071 0039d316-1c4b-4281-b951-d872f2087c98
* Remove static thread pointers from CC, attempt 3aelias@chromium.org2012-11-081-5/+7
| | | | | | | | BUG=152904 Review URL: https://chromiumcodereview.appspot.com/11232051 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166627 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Fix nine patch layer resource management bugs.aelias@chromium.org2012-11-071-8/+2
| | | | | | | | | | | | This switches back to using if (m_resource) in pushPropertiesTo() since it may be called before setNeedsDisplay(). Also, switch to checking if resourceId == 0 instead of backingResourceIsDeleted() since that asserts it's only called on the impl thread. Review URL: https://chromiumcodereview.appspot.com/11377017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166399 0039d316-1c4b-4281-b951-d872f2087c98
* Android: fixes copyright for cc/nine_patch_layer_unittest.cc.bulach@chromium.org2012-11-061-1/+1
| | | | | | | | | | | | The FYI bot step "Check licenses for WebView" is broken. BUG= TEST=android fyi bot is green Review URL: https://chromiumcodereview.appspot.com/11368100 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166232 0039d316-1c4b-4281-b951-d872f2087c98
* cc: Nine patch layer.aelias@chromium.org2012-11-061-0/+142
Review URL: https://chromiumcodereview.appspot.com/11304020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166154 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-06 22:25:38 +0000