Move context-related callbacks into OutputSurface

cc/layer_tree_host_impl.cc

 // Copyright 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "cc/layer_tree_host_impl.h"
 
 #include <algorithm>
 
 #include "base/basictypes.h"
 #include "base/debug/trace_event.h"
@@ skipping 1227 matching lines @@
     renderer_ = SoftwareRenderer::Create(this,
                                          output_surface.get(),
                                          resource_provider.get());
   }
   if (!renderer_)
     return false;
 
   resource_provider_ = resource_provider.Pass();
   output_surface_ = output_surface.Pass();
 
+  output_surface_->RegisterCallbacks();

[piman, 2013/03/15 03:20:38]

It's rather unfortunate that we have this very complicated dance to initialize
the OutputSurface, which is at the API boundary.

What would it take for the callbacks to not behave badly if we were setting them
at Bind time?

+
   if (!visible_)
     renderer_->SetVisible(visible_);
 
   client_->OnCanDrawStateChanged(CanDraw());
 
   // See note in LayerTreeImpl::UpdateDrawProperties.  Renderer needs
   // to be initialized to get max texture size.
   active_tree_->set_needs_update_draw_properties();
   if (pending_tree_)
     pending_tree_->set_needs_update_draw_properties();
@@ skipping 664 matching lines @@
     tile_manager_->SetRecordRenderingStats(debug_state_.recordRenderingStats());
 }
 
 void LayerTreeHostImpl::SavePaintTime(const base::TimeDelta& total_paint_time,
                                       int commit_number) {
   DCHECK(debug_state_.continuousPainting);
   paint_time_counter_->SavePaintTime(total_paint_time, commit_number);
 }
 
 }  // namespace cc