tree: 9e9a4ccfe7b94939f1c9c6af1167dfcb68b61158 [path history] [tgz]
  1. BUILD.gn
  2. DEPS
  3. OWNERS
  4. README.md
  5. accelerators/
  6. accessibility/
  7. accessibility_delegate.h
  8. accessibility_types.h
  9. animation/
  10. app_list/
  11. ash_constants.cc
  12. ash_constants.h
  13. ash_export.h
  14. ash_layout_constants.cc
  15. ash_layout_constants.h
  16. ash_strings.grd
  17. ash_switches.cc
  18. ash_switches.h
  19. ash_touch_exploration_manager_chromeos.cc
  20. ash_touch_exploration_manager_chromeos.h
  21. ash_touch_exploration_manager_chromeos_unittest.cc
  22. ash_view_ids.h
  23. autoclick/
  24. cancel_mode.cc
  25. cancel_mode.h
  26. cast_config_controller.cc
  27. cast_config_controller.h
  28. content/
  29. debug.cc
  30. debug.h
  31. default_accessibility_delegate.cc
  32. default_accessibility_delegate.h
  33. default_wallpaper_delegate.cc
  34. default_wallpaper_delegate.h
  35. dip_unittest.cc
  36. display/
  37. drag_drop/
  38. extended_desktop_unittest.cc
  39. fast_ink/
  40. first_run/
  41. focus_cycler.cc
  42. focus_cycler.h
  43. focus_cycler_unittest.cc
  44. frame/
  45. gpu_support.h
  46. gpu_support_stub.cc
  47. gpu_support_stub.h
  48. high_contrast/
  49. highlighter/
  50. host/
  51. ime/
  52. keyboard/
  53. laser/
  54. login/
  55. login_status.h
  56. magnifier/
  57. media_controller.cc
  58. media_controller.h
  59. metrics/
  60. mojo_interface_factory.cc
  61. mojo_interface_factory.h
  62. multi_profile_uma.cc
  63. multi_profile_uma.h
  64. mus/
  65. mus_property_mirror_ash_unittest.cc
  66. new_window_controller.cc
  67. new_window_controller.h
  68. palette_delegate.h
  69. perftests/
  70. pointer_watcher_adapter_classic.cc
  71. pointer_watcher_adapter_classic.h
  72. pointer_watcher_adapter_classic_unittest.cc
  73. public/
  74. resources/
  75. root_window_controller.cc
  76. root_window_controller.h
  77. root_window_controller_unittest.cc
  78. root_window_settings.cc
  79. root_window_settings.h
  80. rotator/
  81. scoped_root_window_for_new_windows.cc
  82. scoped_root_window_for_new_windows.h
  83. screen_util.cc
  84. screen_util.h
  85. screen_util_unittest.cc
  86. screenshot_delegate.h
  87. session/
  88. shelf/
  89. shell.cc
  90. shell.h
  91. shell/
  92. shell_delegate.h
  93. shell_init_params.h
  94. shell_observer.h
  95. shell_port.cc
  96. shell_port.h
  97. shell_port_classic.cc
  98. shell_port_classic.h
  99. shell_test_api.cc
  100. shell_test_api.h
  101. shell_unittest.cc
  102. shutdown_controller.cc
  103. shutdown_controller.h
  104. shutdown_reason.h
  105. sticky_keys/
  106. strings/
  107. system/
  108. test/
  109. test_screenshot_delegate.cc
  110. test_screenshot_delegate.h
  111. test_shell_delegate.cc
  112. test_shell_delegate.h
  113. tooltips/
  114. touch/
  115. touch_hud/
  116. tray_action/
  117. utility/
  118. virtual_keyboard_controller.cc
  119. virtual_keyboard_controller.h
  120. virtual_keyboard_controller_unittest.cc
  121. wallpaper/
  122. window_user_data.h
  123. window_user_data_unittest.cc
  124. wm/
ash/README.md

Ash

Ash is the “Aura Shell”, the window manager and system UI for Chrome OS. Ash uses the views UI toolkit (e.g. views::View, views::Widget, etc.) backed by the aura native widget and layer implementations.

Ash sits below chrome in the dependency graph (i.e. it cannot depend on code in //chrome). It has a few dependencies on //content, but these are isolated in their own module in //ash/content. This allows targets like ash_unittests to build more quickly.

Tests

Most tests should be added to the ash_unittests target. Tests that rely on //content should be added to ash_content_unittests, but these should be rare.

Tests can bring up most of the ash UI and simulate a login session by deriving from AshTestBase. This is often needed to test code that depends on ash::Shell and the controllers it owns.

Test support code (TestFooDelegate, FooControllerTestApi, etc.) lives in the same directory as the class under test (e.g. //ash/foo rather than //ash/test). Test code uses namespace ash; there is no special “test” namespace.

Mus+ash

Ash is transitioning to use the mus window server and gpu process, found in //services/ui. Ash continues to use aura, but aura is backed by mus. Code to support mus is found in //ash/mus. There should be relatively few differences between the pure aura and the aura-mus versions of ash. Ash can by run in mus mode by passing the --mus command line flag.

Ash is also transitioning to run as a mojo service in its own process. This means that code in chrome cannot call into ash directly, but must use the mojo interfaces in //ash/public/interfaces.

Out-of-process Ash is referred to as “mash” (mojo ash). In-process ash is referred to as “classic ash”. Ash can run in either mode depending on the --mash command line flag.

Historical notes

Ash shipped on Windows for a couple years to support Windows 8 Metro mode. Windows support was removed in 2016.