tree: 4b04961d723de11d807ab577c4435b901248c6e8 [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. devtools/
  36. dip_unittest.cc
  37. display/
  38. drag_drop/
  39. extended_desktop_unittest.cc
  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. host/
  50. ime/
  51. ime_control_delegate.h
  52. key_event_watcher.cc
  53. key_event_watcher.h
  54. keyboard/
  55. laser/
  56. link_handler_model.cc
  57. link_handler_model.h
  58. link_handler_model_factory.cc
  59. link_handler_model_factory.h
  60. login_status.h
  61. magnifier/
  62. media_controller.cc
  63. media_controller.h
  64. metrics/
  65. mojo_interface_factory.cc
  66. mojo_interface_factory.h
  67. multi_profile_uma.cc
  68. multi_profile_uma.h
  69. mus/
  70. mus_property_mirror_ash_unittest.cc
  71. new_window_controller.cc
  72. new_window_controller.h
  73. palette_delegate.h
  74. public/
  75. resources/
  76. root_window_controller.cc
  77. root_window_controller.h
  78. root_window_controller_unittest.cc
  79. root_window_settings.cc
  80. root_window_settings.h
  81. rotator/
  82. scoped_root_window_for_new_windows.cc
  83. scoped_root_window_for_new_windows.h
  84. screen_util.cc
  85. screen_util.h
  86. screen_util_unittest.cc
  87. screenshot_delegate.h
  88. session/
  89. shared/
  90. shelf/
  91. shell.cc
  92. shell.h
  93. shell/
  94. shell_delegate.h
  95. shell_init_params.h
  96. shell_observer.h
  97. shell_port.cc
  98. shell_port.h
  99. shell_unittest.cc
  100. shutdown_controller.cc
  101. shutdown_controller.h
  102. sticky_keys/
  103. strings/
  104. system/
  105. test/
  106. tooltips/
  107. touch/
  108. touch_hud/
  109. tray_action/
  110. utility/
  111. virtual_keyboard_controller.cc
  112. virtual_keyboard_controller.h
  113. virtual_keyboard_controller_unittest.cc
  114. wallpaper/
  115. window_user_data.h
  116. window_user_data_unittest.cc
  117. wm/
  118. wm_display_observer.h
  119. wm_layout_manager.h
  120. wm_transient_window_observer.h
  121. wm_window.cc
  122. wm_window.h
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.