chromium_src.git - central chromium sources

	Commit message (Collapse)	Author	Age	Files	Lines
*	cc/output: cleanup: Remove unnecessary #includes	heejin.r.chung@samsung.com	2014-07-27	1	-1/+3
\| \| \| \| \| \| \| \| \| \|	Remove or move/change #includes to appropriate places/ones. BUG= Review URL: https://codereview.chromium.org/416273005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@285835 0039d316-1c4b-4281-b951-d872f2087c98
*	Initialize overlay validator in GpuBrowserCompositorOutputSurface.	alexst@chromium.org	2014-04-03	1	-4/+5
\| \| \| \| \| \| \| \| \| \|	Plus refactor overlay transform into separate file to use the same type in cc, ozone and context_support. BUG= Review URL: https://codereview.chromium.org/220723006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261301 0039d316-1c4b-4281-b951-d872f2087c98
*	Plumb overlay processing into DirectRenderer.	alexst@chromium.org	2014-03-28	1	-1/+25
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This change tests for overlays inside DirectRenderer::DrawFrame and if new overlay passes were produced, it skips rendering them and forwards the information to FinishDrawingFrame to allow subclasses like GLRenderer and SoftwareRenderer to schedule overlays in a manner specific to their implementation. GLRenderer schedules overlays via ContextSupport. Adds more tests to ensure overlay quads are not drawn and if no overlays are present, no quads are skipped. BUG= Review URL: https://codereview.chromium.org/208213003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@260267 0039d316-1c4b-4281-b951-d872f2087c98
*	Start of hardware overlay support in CC with Ubercompositor.	alexst@chromium.org	2014-03-20	1	-0/+17
	I'm trying to introduce everything as small unit tested pieces. This adds some machinery for checking if quads inside a render pass could be placed into an overlay. A capability checker is added to the output surface, so that a particular overlay configuration could be validated against a specific display device. If an external monitor is plugged in, its output surface may behave differently that that of the primary on a laptop, for example. The intention is for OverlayCandidates checker to be created as part of BrowserCompositorOutputSurface where the actual hardware knowledge can be delegated to the Ozone platform and the HW specific bits can live there, leaving CC and content platform agnostic. BUG= Review URL: https://codereview.chromium.org/197223003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@258209 0039d316-1c4b-4281-b951-d872f2087c98