Propagate DPI information to web-app.

remoting/client/plugin/chromoting_instance.cc

Index: remoting/client/plugin/chromoting_instance.cc
diff --git a/remoting/client/plugin/chromoting_instance.cc b/remoting/client/plugin/chromoting_instance.cc
index 77cd55fdc4e10a4b4d8513f9701ef43f13215535..60afe2b19d35282d6918e0cf25875ec6a60af640 100644
--- a/remoting/client/plugin/chromoting_instance.cc
+++ b/remoting/client/plugin/chromoting_instance.cc
@@ -352,10 +352,13 @@ bool ChromotingInstance::HandleInputEvent(const pp::InputEvent& event) {
   return input_handler_->HandleInputEvent(event);
 }
 
-void ChromotingInstance::SetDesktopSize(int width, int height) {
+void ChromotingInstance::SetDesktopSize(const SkISize& size,
+                                        const SkIPoint& dpi) {
   scoped_ptr<base::DictionaryValue> data(new base::DictionaryValue());
-  data->SetInteger("width", width);
-  data->SetInteger("height", height);
+  data->SetInteger("width", size.width());
+  data->SetInteger("height", size.height());
+  data->SetInteger("x_dpi", dpi.x());

[Wez, 2012/07/19 01:00:42]

nit: I was going to suggest only passing x_dpi and y_xpi if they are non-zero,
i.e. if the host sent them, but I notice that you're having the plugin fake them
if they're not already present; is that worth it? There's not really any
difference between a client that doesn't understand the DPI fields (and so won't
include them here) and one that does, but is talking to an older host.

[Jamie, 2012/07/19 23:00:06]

Done.

+  data->SetInteger("y_dpi", dpi.y());
   PostChromotingMessage("onDesktopSize", data.Pass());
 }