[Chromoting] Initial plumbing for cursor shape.

remoting/client/chromoting_view.h

Index: remoting/client/chromoting_view.h
diff --git a/remoting/client/chromoting_view.h b/remoting/client/chromoting_view.h
index af9a5ac850f0945b57125435d95bf7285552ab0c..1806210a41aded5cd0f0c3b9ebf7556aa2d914f2 100644
--- a/remoting/client/chromoting_view.h
+++ b/remoting/client/chromoting_view.h
@@ -7,6 +7,7 @@
 
 #include "base/basictypes.h"
 #include "remoting/protocol/connection_to_host.h"
+#include "remoting/protocol/cursor_shape_stub.h"
 
 namespace remoting {
 
@@ -17,7 +18,7 @@ class ClipboardStub;
 // ChromotingView defines the behavior of an object that draws a view of the
 // remote desktop. Its main function is to render the update stream onto the
 // screen.
-class ChromotingView {
+class ChromotingView : public protocol::CursorShapeStub {

[Wez, 2012/05/23 00:01:57]

Expose CursorShapeStub via a getter, as for ClipboardStub.

[garykac, 2012/05/26 01:58:01]

ClipboardStub is a getter because is passes the messages on to the
ChromotingInstance for handling.

CursorShapeStub messages are handled here in the view. I don't think it makes
sense to send them anywhere else.

[Wez, 2012/05/29 18:02:54]

That's a detail of this implementation, not intrinsic to the interface.  And it
would be perfectly reasonable to hive the cursor shape setting code off into a
separate component within PepperView, for example.

  public:
   virtual ~ChromotingView() {}