Move screen capturers from remoting/capturer to media/video/capturer/screen

media/video/capture/screen/screen_capturer_mock_objects.cc

+// 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.
+
+#include "media/video/capture/screen/screen_capturer_mock_objects.h"
+
+#include "media/video/capture/screen/screen_capturer.h"
+#include "testing/gmock/include/gmock/gmock.h"
+
+namespace media {
+
+MockScreenCapturer::MockScreenCapturer() {}
+
+MockScreenCapturer::~MockScreenCapturer() {}
+
+MockScreenCapturerDelegate::MockScreenCapturerDelegate() {

[scherkus (not reviewing), 2013/01/25 00:30:36]

nit: you're inconsistent on {} vs {\n}

FWIW I prefer the former and the clang-based C++ formatter agrees with me ;)

[Sergey Ulanov, 2013/01/25 00:49:50]

Fixed.
I agree, but several times I was asked to use {\n} when getting my changes
reviewed in various parts of chrome. I think it's more consistent with the rest
of chromium code. Also {} becomes less readable for constructors with member
initializers.
How can I try it?

[scherkus (not reviewing), 2013/01/25 05:03:40]

Yeah media/ code attempts to use {} for single line functions but {\n} if it
it's more than one line for reasons you describe (i.e., readability w/
initializers)... but same-file consistency is good enough for me
Sent you an email.

+}
+
+MockScreenCapturerDelegate::~MockScreenCapturerDelegate() {
+}
+
+void MockScreenCapturerDelegate::OnCursorShapeChanged(
+    scoped_ptr<MouseCursorShape> cursor_shape) {
+  // Notify the mock method.
+  OnCursorShapeChangedPtr(cursor_shape.get());
+}
+
+}  // namespace media