[Webkit-unassigned] [Bug 39672] Make sure skia is not Chromium specific

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=39672





--- Comment #10 from Stephen White <senorblanco at chromium.org>  2010-08-30 09:02:15 PST ---
(In reply to comment #9)
> (In reply to comment #8)
> > Not sure what the status of this patch is, but it looks like an ok workaround for now.
> > 
> > Ideally, we'd upstream all the stuff from the chromium repo (chromium/src/skia/ext) into Skia proper, then everyone could use it.  Let me know if you're interested in working on that, and I can help you land it in Skia.
> 
> I think it is a good idea to upstream Chromium's chromium/src/skia/ext to Skia repo so that other WebKit ports can use it. Please help me do the job.

After looking at it a bit, it seems as if this is not quite as clean as I thought.  It seems that skia/ext depends on some things in chromium/base.  So the first job would be to get rid of those dependencies.  This will require some knowledge of the chromium project, and some ideas of how to replace those dependencies (I don't have all the answers here).

After that, it would be a matter of reformatting the code to be more skia-friendly (getting rid of chrome-specific relative paths, for example), and then creating a patch for Skia to add the content of the (new) /ext directory, and uploading it to codereview.appspot.com for review.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.