Module webrender_api::image

source ·

Modules

Structs

  • Metadata (but not storage) for a blob image.
  • An opaque identifier describing a blob image registered with WebRender. This is used as a handle to reference blob images, and can be used as an image in display items.
  • Input parameters for the BlobImageRasterizer.
  • A key identifying blob image rasterization work requested from the blob image rasterizer.
  • The data that an external client should provide about an external image. For instance, if providing video frames, the application could call wr.render() whenever a new video frame is ready. Note that the UV coords are supplied in texel-space!
  • Descriptor for external image resources. See ImageData.
  • An arbitrary identifier for an external image provided by the application. It must be a unique identifier for each external image.
  • Metadata (but not storage) describing an image In WebRender.
  • Various flags that are part of an image descriptor.
  • An opaque identifier describing an image registered with WebRender. This is used as a handle to reference images, and is used as the hash map key for the actual image storage in the ResourceCache.
  • Representation of a rasterized blob image. This is obtained by passing BlobImageData to the embedding via the rasterization callback.

Enums

  • Error code for when blob rasterization failed.
  • Specifies the color depth of an image. Currently only used for YUV images.
  • The possible states of a Dirty rect.
  • The source for an external image.
  • Storage format identifier for externally-managed images.
  • Specifies the type of texture target in driver terms.
  • Represents the backing store of an arbitrary series of pixels for display by WebRender. This storage can take several forms.
  • Specifies the format of a series of pixels, in driver terms.

Constants

  • The default tile size for blob images and regular images larger than the maximum texture size.

Traits

  • A group of rasterization requests to execute synchronously on the scene builder thread.
  • A handler on the render backend that can create rasterizer objects which will be sent to the scene builder thread to execute the rasterization.
  • The resources exposed by the resource cache available for use by the blob rasterizer.
  • The interfaces that an application can implement to support providing external image buffers. When the application passes an external image to WR, it should keep that external image life time. People could check the epoch id in RenderNotifier at the client side to make sure that the external image is not used by WR. Then, do the clean up for that external image.

Type Aliases