06e73fff15
- Add Views header files in a new include/views directory. - Add initial top-level window (CefWindow), control (CefBrowserView, CefLabelButton, CefMenuButton, CefPanel, CefScrollView, CefTextfield) and layout (CefBoxLayout, CefFlowLayout) support. See libcef/browser/views/view_impl.h comments for implementation details. - Add Views example usage in cefclient and cefsimple and Views unit tests in cef_unittests. Pass the `--use-views` command-line flag to cefclient, cefsimple and cef_unittests to run using the Views framework instead of platform APIs. For cefclient and cefsimple this will create the browser window and all related functionality using the Views framework. For cef_unittests this will run all tests (except OSR tests) in a Views-based browser window. Views- specific unit tests (`--gtest_filter=Views*`) will be run even if the the `--use-views` flag is not specified. - Pass the `--hide-frame` command-line flag to cefclient to demo a frameless Views-based browser window. - Pass the `--hide-controls` command-line flag to cefclient to demo a browser window without top controls. This also works in non-Views mode. - Pass the `--enable-high-dpi-support` command-line flag to cef_unittests on Windows to test high-DPI support on a display that supports it. - Add CefImage for reading/writing image file formats. - Add CefBrowser::DownloadImage() for downloading image URLs as a CefImage representation. This is primarily for loading favicons. - Add CefMenuModel::CreateMenuModel() and CefMenuModelDelegate for creating custom menus. This is primarily for use with CefMenuButton. - Add CefBrowser::TryCloseBrowser() helper for closing a browser. Also improve related documentation in cef_life_span_handler.h. - Rename cef_page_range_t to cef_range_t. It is now also used by CefTextfield. - Remove CefLifeSpanHandler::RunModal() which is never called. - Add draggable regions example to cefclient. |
||
|---|---|---|
| .. | ||
| patches | ||
| README.txt | ||
| patch.cfg | ||
README.txt
There may be instances where CEF requires changes to the Chromium/WebKit code base that are not desired by the Chromium/WebKit projects as a whole. To address this situation the CEF project adds a patch capability as part of the CEF GYP project generation step. The patch capability works as follows: 1. The CEF developer creates one or more patch files containing all required changes to the Chromium/WebKit code base and places those patch files in the "patches" subdirectory. 2. The CEF developer adds an entry for each patch file in the "patch.cfg" file. 3. CEF applies the patches to the Chromium/WebKit source tree using the patcher.py tool in the tools directory. If necessary the patcher.py tool also rewrites the "patch_state.h" file which defines the CEF_PATCHES_APPLIED preprocessor value. To disable automatic application of patches to the Chromium/WebKit code base create an empty "NOPATCH" file in the "patch" directory. Sections of the CEF code base that otherwise require patches will be disabled using the CEF_PATCHES_APPLIED preprocessor value defined in the "patch_state.h" file. Be warned that not applying all required patches may break important CEF functionality.