Convert Chromoting plugin logging to appear in client UI

remoting/client/plugin/chromoting_instance.h

Index: remoting/client/plugin/chromoting_instance.h
diff --git a/remoting/client/plugin/chromoting_instance.h b/remoting/client/plugin/chromoting_instance.h
index c1c68d67f99019f1df53b131decbe2072c2f01fe..45d250b86a909b259f46aa0c0e4d9c346bc4d4b3 100644
--- a/remoting/client/plugin/chromoting_instance.h
+++ b/remoting/client/plugin/chromoting_instance.h
@@ -19,6 +19,7 @@
 #include "ppapi/cpp/var.h"
 #include "remoting/client/client_context.h"
 #include "remoting/client/plugin/chromoting_scriptable_object.h"
+#include "remoting/client/plugin/pepper_client_logger.h"
 #include "remoting/protocol/connection_to_host.h"
 
 class MessageLoop;
@@ -85,7 +86,8 @@ class ChromotingInstance : public pp::Instance {
   // Called by ChromotingScriptableObject to set scale-to-fit.
   void SetScaleToFit(bool scale_to_fit);
 
-  void LogDebugInfo(const std::string& info);
+  void Log(int severity, const char* format, ...);

[Sergey Ulanov, 2011/05/18 23:56:26]

Do we need this methods? Maybe it's better to add logger() that would return
pointer to |logger_|?

[garykac, 2011/05/19 21:14:36]

I originally had that, but found that:

   instance_->getLogger()->Log(...)

was a lot more irritating to deal with than simply:

   instance_->Log(...)

We type these log lines fairly frequently in the code so the convenience was
nice.

+  void VLog(int verboselevel, const char* format, ...);
 
   // Return statistics record by ChromotingClient.
   // If no connection is currently active then NULL will be returned.
@@ -118,6 +120,8 @@ class ChromotingInstance : public pp::Instance {
   // connection.
   scoped_refptr<PepperXmppProxy> xmpp_proxy_;
 
+  PepperClientLogger logger_;
+
   // JavaScript interface to control this instance.
   // This wraps a ChromotingScriptableObject in a pp::Var.
   pp::Var instance_object_;