tree: 4719d93fa31f2301e4773f947f38d3730c4dcde0 [path history] [tgz]
  1. BUILD.gn
  2. DEPS
  3. OWNERS
  4. README.md
  5. accelerators/
  6. accessibility_delegate.h
  7. accessibility_types.h
  8. animation/
  9. app_list/
  10. ash_constants.cc
  11. ash_constants.h
  12. ash_export.h
  13. ash_layout_constants.cc
  14. ash_layout_constants.h
  15. ash_strings.grd
  16. ash_switches.cc
  17. ash_switches.h
  18. ash_touch_exploration_manager_chromeos.cc
  19. ash_touch_exploration_manager_chromeos.h
  20. ash_touch_exploration_manager_chromeos_unittest.cc
  21. ash_view_ids.h
  22. aura/
  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. first_run/
  40. focus_cycler.cc
  41. focus_cycler.h
  42. focus_cycler_unittest.cc
  43. frame/
  44. gpu_support.h
  45. gpu_support_stub.cc
  46. gpu_support_stub.h
  47. high_contrast/
  48. host/
  49. ime/
  50. keyboard/
  51. laser/
  52. link_handler_model.cc
  53. link_handler_model.h
  54. link_handler_model_factory.cc
  55. link_handler_model_factory.h
  56. login/
  57. login_status.h
  58. magnifier/
  59. media_controller.cc
  60. media_controller.h
  61. metrics/
  62. mojo_interface_factory.cc
  63. mojo_interface_factory.h
  64. multi_profile_uma.cc
  65. multi_profile_uma.h
  66. mus/
  67. mus_property_mirror_ash_unittest.cc
  68. new_window_controller.cc
  69. new_window_controller.h
  70. palette_delegate.h
  71. perftests/
  72. public/
  73. resources/
  74. root_window_controller.cc
  75. root_window_controller.h
  76. root_window_controller_unittest.cc
  77. root_window_settings.cc
  78. root_window_settings.h
  79. rotator/
  80. scoped_root_window_for_new_windows.cc
  81. scoped_root_window_for_new_windows.h
  82. screen_util.cc
  83. screen_util.h
  84. screen_util_unittest.cc
  85. screenshot_delegate.h
  86. session/
  87. shelf/
  88. shell.cc
  89. shell.h
  90. shell/
  91. shell_delegate.h
  92. shell_init_params.h
  93. shell_observer.h
  94. shell_port.cc
  95. shell_port.h
  96. shell_unittest.cc
  97. shutdown_controller.cc
  98. shutdown_controller.h
  99. shutdown_reason.h
  100. sticky_keys/
  101. strings/
  102. system/
  103. test/
  104. tooltips/
  105. touch/
  106. touch_hud/
  107. tray_action/
  108. utility/
  109. virtual_keyboard_controller.cc
  110. virtual_keyboard_controller.h
  111. virtual_keyboard_controller_unittest.cc
  112. wallpaper/
  113. window_user_data.h
  114. window_user_data_unittest.cc
  115. 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.

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.