Add PlatformPictureSkia and RecordingPlatformDeviceSkia.

skia/ext/platform_canvas.h

Index: skia/ext/platform_canvas.h
diff --git a/skia/ext/platform_canvas.h b/skia/ext/platform_canvas.h
index cbeb95b2bbe252cf5c5ebc7bd3abeeb3ad29dcf8..11729bfbd277b4fe98d255cd199ed810db4092ac 100644
--- a/skia/ext/platform_canvas.h
+++ b/skia/ext/platform_canvas.h
@@ -115,10 +115,9 @@ SK_API SkCanvas* CreateBitmapCanvas(int width, int height, bool is_opaque);
 // and where it is possible to recover gracefully from the failed allocation.
 SK_API SkCanvas* TryCreateBitmapCanvas(int width, int height, bool is_opaque);
 

[reed1, 2012/09/24 21:04:01]

So now a canvas/device will report DIRECT or INDIRECT support. Does this mean
that if we have a device that returns DIRECT (the new code written for NPAPI),
that we must always do that, even for callers like Form Controls that would be
fine with the cheaper INDIRECT?

Might it make sense for the caller to specify their requirements, so that more
efficient clients need never trigger the DIRECT path?

-// Returns true if native platform routines can be used to draw on the
-// given canvas. If this function returns false, BeginPlatformPaint will
-// return NULL PlatformSurface.
-SK_API bool SupportsPlatformPaint(const SkCanvas* canvas);
+// Returns support for native platform routines.
+SK_API PlatformDevice::PlatformPaint PlatformPaintSupport(
+    const SkCanvas* canvas);
 
 // Draws into the a native platform surface, |context|.  Forwards to
 // DrawToNativeContext on a PlatformDevice instance bound to the top device.