cc: Include pictures in trace output for DisplayItemLists

cc/resources/drawing_display_item.cc

Index: cc/resources/drawing_display_item.cc
diff --git a/cc/resources/drawing_display_item.cc b/cc/resources/drawing_display_item.cc
index f8d3c62ce6f1c909954dee1f338ea5878250ab4e..294858213b90f60c8008e07309e0220ab82efe38 100644
--- a/cc/resources/drawing_display_item.cc
+++ b/cc/resources/drawing_display_item.cc
@@ -31,6 +31,13 @@ void DrawingDisplayItem::Raster(SkCanvas* canvas,
   canvas->restore();
 }
 
+void DrawingDisplayItem::RasterForTracing(SkCanvas* canvas) const {

[vmpstr, 2015/01/08 21:44:34]

This seems to be basically ::Raster with nullptr as callback (except it would
use drawPicture instead of playback). 

Is there a reason this has to be a different function?

[ajuma, 2015/01/08 22:20:58]

We need playback instead of drawPicture to make the tracing output useful. If we
use drawPicture, the resulting SkPicture is just a sequence of drawPicture ops,
one for each DrawingDisplayItem. The picture debugger in about:tracing doesn't
go deeper for drawPicture ops, so all we see is a sequence of drawPicture ops
and not much else. With playback, the SkPicture consists of the individual ops. 

[vmpstr, 2015/01/08 22:45:59]

Ah I see. FWIW, you can just Raster and give is some small class DontAbort :
public SkDrawPictureCallback { bool abortDrawing() override { return false; } };
type of thing. However, this works as well.

Either way, can you make a comment here that explains why this should be
different (or why we need to pass a don't abort callback if you go that route)?

[ajuma, 2015/01/08 23:16:11]

Added a comment.

+  canvas->save();
+  canvas->translate(location_.x(), location_.y());
+  picture_->playback(canvas);
+  canvas->restore();
+}
+
 bool DrawingDisplayItem::IsSuitableForGpuRasterization() const {
   return picture_->suitableForGpuRasterization(NULL);
 }