Mandoline: Allow submitting CompositorFrames directly to mojo::Views

components/view_manager/public/cpp/view.h

Index: components/view_manager/public/cpp/view.h
diff --git a/components/view_manager/public/cpp/view.h b/components/view_manager/public/cpp/view.h
index 3d6ac527c36132dfea7f4d66a002d4205ccef58f..d61bf7f68289e39a041d0845d0030dccbdf08e4e 100644
--- a/components/view_manager/public/cpp/view.h
+++ b/components/view_manager/public/cpp/view.h
@@ -61,6 +61,9 @@ class View {
 
   const ViewportMetrics& viewport_metrics() { return *viewport_metrics_; }
 
+  void RequestCompositorFrameReceiver(
+      InterfaceRequest<CompositorFrameReceiver> receiver);

[sky, 2015/08/25 17:11:12]

I think we would be better served by not exposing the raw pipe here, but instead
wrapping the return value in an object that owns the binding. I think this will
let you better deal with returning resources to the client too.

[Fady Samuel, 2015/08/25 23:39:30]

I absolutely agree. I'm working on it now but I'd prefer doing it in a separate
patch so this one doesn't grow too much.

+
   // Returns the set of string to bag of byte properties. These properties are
   // shared with the view manager.
   const SharedProperties& shared_properties() const { return properties_; }