Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(2123)

Issue 6245078: Gradient CustomStage integration (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 1 month ago by TomH
Modified:
12 years ago
Reviewers:
bsalomon
Base URL:
http://skia.googlecode.com/svn/trunk/
Visibility:
Public.

Description

This works.

Patch Set 1 #

Patch Set 2 : Update to r4116, resolving duplicated code #

Patch Set 3 : Update to r4128, resolving resource issues #

Patch Set 4 : Down with SampleMode #

Total comments: 12
Unified diffs Side-by-side diffs Delta from patch set Stats (+50 lines, -382 lines) Patch
M include/gpu/GrSamplerState.h View 1 2 3 7 chunks +2 lines, -75 lines 4 comments Download
M src/gpu/SkGpuDevice.cpp View 1 2 3 6 chunks +17 lines, -17 lines 3 comments Download
M src/gpu/effects/GrGradientEffects.cpp View 1 2 1 chunk +1 line, -1 line 2 comments Download
M src/gpu/gl/GrGLProgram.h View 1 2 3 chunks +0 lines, -16 lines 1 comment Download
M src/gpu/gl/GrGLProgram.cpp View 1 2 7 chunks +8 lines, -206 lines 1 comment Download
M src/gpu/gl/GrGpuGL.h View 1 2 3 1 chunk +0 lines, -1 line 1 comment Download
M src/gpu/gl/GrGpuGL_program.cpp View 1 2 3 7 chunks +3 lines, -64 lines 0 comments Download
M src/gpu/gl/GrGpuGL_unittest.cpp View 1 2 5 chunks +19 lines, -2 lines 0 comments Download

Messages

Total messages: 3
TomH
Muahaha. They laughed at me when I said I had a CL that removed 40 ...
12 years ago (2012-06-01 20:27:49 UTC) #1
bsalomon
I love this change! LGTM (but let's save the documentation of the parameters that specify ...
12 years ago (2012-06-01 20:37:27 UTC) #2
TomH
12 years ago (2012-06-01 20:44:12 UTC) #3
On 2012/06/01 20:37:27, bsalomon wrote:
> On 2012/06/01 20:27:50, TomH wrote:
> > We might want to make sure we've got these semantics documented somewhere
> else?
> Yes, should we port this documentation GrGradientEffects.h?
Done.

> src/gpu/SkGpuDevice.cpp:16: #include "SkGpuDevice.h"
> Let's move this include to the top (since it is the decl of the class being
> defined here)
Done.

> On 2012/06/01 20:27:50, TomH wrote:
> > Next step (to make Mike happy): write shader::getCustomStage() and not have
to
> > bother with asABitmap() (? assuming we don't have to worry too much about
the
> > params being passed in invalidating the assumptions of our custom stage
> > implementations - but then we should probably just be improving those).
> 
> I think this is "a" next step but IMO isn't "the" next step. I think we should
> keep generalizing what stages can do (and not do).
Yes, "a" next step in the grand scheme of things. Get around to it when we want
to bother with keeping Mike happy.

Committed (in a fit of folly late on a Friday) as r4129.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b