A GPU based renderer for the web.
It serves as an experimental render backend for Servo, but it can also be used as such in a standalone application.
WebRender currently depends on FreeType
The main entry point to WebRender is the
Renderer::new(...) you get a
Renderer, as well as
Renderer is responsible to render the
previously processed frames onto the screen.
RenderApi instance, which is responsible for managing resources
and documents. A worker thread is used internally to untie the workload from the application
thread and therefore be able to make better use of multicore systems.
What is referred to as a
frame, is the current geometry on the screen.
A new Frame is created by calling
RenderApi. When the geometry is processed, the application will be
informed via a
RenderNotifier, a callback which you pass to
More information about stacking contexts.
set_display_list() also needs to be supplied with
BuiltDisplayLists. These are obtained by finalizing a
DisplayListBuilder. These are used to draw your geometry. But it
doesn’t only contain trivial geometry, it can also store another
StackingContext, as they’re nestable.