cef/libcef/common/alloy
Marshall Greenblatt 8424f166cc Use the same pak files for the Alloy and Chrome runtimes (see issue #2969)
Chrome currently uses chrome_100_percent.pak, chrome_200_percent.pak,
resources.pak and locales/<locale>.pak files. This change adds CEF
resources to those existing pak files and updates the Alloy runtime to
use them instead of the previous CEF-specific pak files (cef.pak,
cef_100_percent.pak, cef_200_percent.pak, cef_extensions.pak,
devtools_resources.pak) which are no longer generated.

The addition of Chrome resources results in an ~16% (~4.1MB) increase in total
combined pak file size vs. the previous CEF-specific pak files. While a size
increase is not ideal for the Alloy runtime, it seems preferable to the
alternative of distributing separate (and partially duplicated) pak files for
each runtime, which would have added ~9.8MB to the total binary distribution
size.
2021-02-28 16:51:37 -05:00
..
alloy_content_client.cc Update to Chromium version 88.0.4324.0 (#827102) 2020-12-04 15:43:33 -05:00
alloy_content_client.h Add CefAppManager and remove global ContentClient accessors (see issue #2969) 2020-06-29 16:17:58 -04:00
alloy_main_delegate.cc Use the same pak files for the Alloy and Chrome runtimes (see issue #2969) 2021-02-28 16:51:37 -05:00
alloy_main_delegate.h Make CefBrowserContext an abstract base class (see issue #2969) 2020-07-01 15:35:07 -04:00
alloy_main_runner_delegate.cc Rename the current CEF runtime to Alloy (see issue #2969) 2020-06-29 16:17:41 -04:00
alloy_main_runner_delegate.h Rename the current CEF runtime to Alloy (see issue #2969) 2020-06-29 16:17:41 -04:00