[Chromoting] Initial plumbing for cursor shape.

remoting/client/chromoting_view.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef REMOTING_CLIENT_CHROMOTING_VIEW_H_
 #define REMOTING_CLIENT_CHROMOTING_VIEW_H_
 
 #include "base/basictypes.h"
 #include "remoting/protocol/connection_to_host.h"
+#include "remoting/protocol/cursor_shape_stub.h"
 
 namespace remoting {
 
 namespace protocol {
 class ClipboardStub;
 }  // namespace protocol
 
 // 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() {}
 
   // Initialize the common structures for the view.
   virtual bool Initialize() = 0;
 
   // Free up resources allocated by this view.
   virtual void TearDown() = 0;
 
   // Record the update the state of the connection, updating the UI as needed.
   virtual void SetConnectionState(protocol::ConnectionToHost::State state,
                                   protocol::ErrorCode error) = 0;
 
   // Get the view's ClipboardStub implementation.
   virtual protocol::ClipboardStub* GetClipboardStub() = 0;
 };
 
 }  // namespace remoting
 
 #endif  // REMOTING_CLIENT_CHROMOTING_VIEW_H_