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