remoting: Create composing capturer and mouse shape pump in pairs

DesktopCaptureOptions are used by both the mouse cursor monitor
as well as the desktop capturer. When composing the video with
mouse cursor, these two object rely on shared data in capture
options (e.g. shared X connection and shared screen cast for X11
and Wayland respectively).

In case of X11 implementation, there is currently only
one mouse shape pump that is used for all the video streams.
In case of Wayland, we have a single stream per capturer and it
makes sense to have a single pump for that stream. To that
end this change adds, a composer + cursor monitor manager class
to handle the differences in implementation between Wayland
and X implementation. This manager class will be responsible
for creating the condition video composer along with any
mouse shape pump needed with it. This new class is used by the
desktop environment class to create the composer (and implicitly
mouse shape pump / cursor monitor).

Bug: chromium:1291247
Change-Id: Ifd86bfae141aff46f831194ac7f2b886547dc6fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3857881
Commit-Queue: Salman Malik <salmanmalik@chromium.org>
Reviewed-by: Lambros Lambrou <lambroslambrou@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1043957}
17 files changed
tree: 01732942bbed62a2220b215b3ade7e544b93db9b
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.