[Remoting Android] DisplayUpdaterFactory cleanups

remoting/client/plugin/pepper_video_renderer.h

Index: remoting/client/plugin/pepper_video_renderer.h
diff --git a/remoting/client/plugin/pepper_video_renderer.h b/remoting/client/plugin/pepper_video_renderer.h
index 802a29c80ac3de52c5ceaf9919b49fdc9e3f5c50..b42339ad30ca4e12210a3d59d71ca219d2261e0f 100644
--- a/remoting/client/plugin/pepper_video_renderer.h
+++ b/remoting/client/plugin/pepper_video_renderer.h
@@ -48,10 +48,10 @@ class PepperVideoRenderer : public protocol::VideoRenderer {
 
   // Initializes the renderer. |instance| and |event_handler| must outlive the
   // renderer. Returns false if the renderer cannot be initialized.
-  virtual bool Initialize(pp::Instance* instance,
-                          const ClientContext& context,
-                          EventHandler* event_handler,
-                          protocol::PerformanceTracker* perf_tracker) = 0;
+  virtual bool InitializePepper(pp::Instance* instance,

[Sergey Ulanov, 2016/06/28 17:59:50]

This now overlaps with Initialize(). Remove |context| and |perf_tracker|
arguments from this methods. Then ChromotingInstance will need to call both
InitializePepper() and then Initialize()
Also maybe better to call it SetPepperContext() or something like that, to make
the purpose clearer.

[Yuwei, 2016/06/28 18:46:06]

Done.

+                                const ClientContext& context,
+                                EventHandler* event_handler,
+                                protocol::PerformanceTracker* perf_tracker) = 0;
 
   // Must be called whenever the plugin view changes.
   virtual void OnViewChanged(const pp::View& view) = 0;