blimp: Move compositing, input and render widget feature to client/core.

blimp/client/core/blimp_client_context_impl.cc

Index: blimp/client/core/blimp_client_context_impl.cc
diff --git a/blimp/client/core/blimp_client_context_impl.cc b/blimp/client/core/blimp_client_context_impl.cc
index f90b1dc02b222929b3e0851a1a240809064d7aa0..55294f9f54e8bf6b690c7510df7c753c3a35d8f1 100644
--- a/blimp/client/core/blimp_client_context_impl.cc
+++ b/blimp/client/core/blimp_client_context_impl.cc
@@ -5,6 +5,7 @@
 #include "blimp/client/core/blimp_client_context_impl.h"
 
 #include "base/bind.h"
+#include "base/lazy_instance.h"
 #include "base/memory/ptr_util.h"
 #include "base/message_loop/message_loop.h"
 #include "base/threading/sequenced_task_runner_handle.h"
@@ -23,6 +24,9 @@ namespace client {
 namespace {
 const char kDefaultAssignerUrl[] =
     "https://blimp-pa.googleapis.com/v1/assignment";
+
+// This should go elsewhere when we start setting up the feature code.
+base::LazyInstance<RenderWidgetFeature> g_render_widget_feature;

[nyquist, 2016/08/16 23:14:57]

Discussed with dtrainor@. I think for now BlimpClientContextImpl can own it, and
you can pass a pointer to BCM in the constructor? WDYT?
The registration can happen in BCCI:BCCI() I think.

[Khushal, 2016/08/18 03:16:32]

Makes sense. Done.
That is where we do start up the ThreadPipeManager and rest of the net code.

 }  // namespace
 
 // This function is declared in //blimp/client/public/blimp_client_context.h,
@@ -48,7 +52,8 @@ BlimpClientContextImpl::BlimpClientContextImpl(
     : BlimpClientContext(),
       io_thread_task_runner_(io_thread_task_runner),
       file_thread_task_runner_(file_thread_task_runner),
-      blimp_contents_manager_(new BlimpContentsManager),
+      blimp_contents_manager_(
+          new BlimpContentsManager(true, g_render_widget_feature.Pointer())),
       weak_factory_(this) {
   net_components_.reset(new ClientNetworkComponents(
       base::MakeUnique<CrossThreadNetworkEventObserver>(