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