Porting from 1.2 to 1.3

Portions of Config have been moved to ViewConfig

You can now set a number of config options on a per-View basis (instead of setting these values globally). You do this by passing a new ViewConfig struct to Renderer::CreateView().

For example, if you're using the low-level Renderer API, you can now have each View use the CPU or GPU renderer via the new is_accelerated option in ViewConfig.

///
/// When enabled, the View will be rendered to an offscreen GPU texture
/// using the GPU driver set in Platform::set_gpu_driver. You can fetch
/// details for the texture via View::render_target.
///
/// When disabled (the default), the View will be rendered to an offscreen
/// pixel buffer. This pixel buffer can optionally be provided by the user--
/// for more info see <Ultralight/platform/Surface.h> and View::surface.
///
bool is_accelerated = false;

You can also now set a separate device scale (DPI scale) for each View via initial_device_scale:

double initial_device_scale = 1.0;

This device scale can be changed during runtime via View::set_device_scale().

CPU and GPU Renderers Now Use the Same Compositing Pipeline

The CPU and GPU renderers previously used separate compositing/blending math and font compositing routines which caused subtle differences in the visual output (especially when alpha-blending certain transparent PNGs and CSS opacity layers).

The pipelines have now been rewritten to blend in sRGB space which better matches what Chrome and Firefox are doing in their renderers.

Furthermore, alpha correction of fonts has been improved to be more robust when rendering against transparent backgrounds (important for compositing text in games).

Multi-Window Support in AppCore

AppCore now allows users to create multiple windows in a single app-- you no longer need to call App::set_window()-- just create a window and it will appear on screen.

You can also now create hidden windows and show them at a later time (important for pre-loading content).

You Must Now Call App::Quit() Manually in AppCore

Previously, apps would automatically call App::Quit() when the window was closed.

Since apps now support multiple windows, it's indetermine which one of these should cause the app to quit.

For that reason, you must now call App::Quit() yourself to exit the run loop. We recommend handling WindowListener::OnClose() and calling this yourself when your "main window" is closed.