The Plotters backend API crate. This is a part of Plotters, the Rust drawing and plotting library, for more details regarding the entire Plotters project, please check the main crate.
This is the crate that used as the connector between Plotters and different backend crates. Since Plotters 0.3, all the backends has been hosted as seperate crates for the usability and maintainability reasons.
At the same time, Plotters is now supporting third-party backends and all the backends are now supports "plug-and-play": To use a external backend, just depends on both the Plotters main crate and the third-party backend crate.
To create a new Plotters backend, this crate should be imported to the crate and the trait DrawingBackend should
be implemented. It's highly recommended that the third-party backend uses
plotters-backend by version specification
For more details, see the compatibility note.
If the backend only implements DrawingBackend::draw_pixel, the default CPU rasterizer will be used to give your backend ability of drawing different shapes. For those backend that supports advanced drawing instructions, such as, GPU acelerated shape drawing, all the provided trait method can be overriden from the specific backend code.
If your backend have text rendering ability, you may want to override the DrawingBackend::estimate_text_size to avoid wrong spacing, since the Plotters default text handling code may behaves differently from the backend in terms of text rendering.
Backend might render the image realtimely/animated, for example, a GTK backend for realtime display or a GIF image rendering. To support these
features, you need to play with
present method. The following figure illustrates how Plotters operates a drawing backend.
ensure_prepared- Called before each time when plotters want to draw. This function should initialize the backend for current frame, if the backend is already prepared for a frame, this function should simply do nothing.
present- Called when plotters want to finish current frame drawing
.ensure_prepared() && +-------------+ +-------------+ .draw_pixels() +--------------+ drop |Start drwaing|--->|Ready to draw| ------------------------+---->|Finish 1 frame| ---------> +-------------+ +-------------+ | +--------------+ ^ ^ | | | +------------------------------- + | | continue drawing | +----------------------------------------------------------------+ start render the next frame .present()
- For both animated and static drawing,
DrawingBackend::presentindicates current frame should be flushed.
- For both animated and static drawing,
DrawingBackend::ensure_preparedis called every time when plotters need to draw.
- For static drawing, the
DrawingBackend::presentis only called once manually, or from the Drop impl for the backend.
- For dynamic drawing, frames are defined by invocation of
DrawingBackend::present, everything prior the invocation should belongs to previous frame
Since Plotters v0.3, plotters use the "plug-and-play" schema to import backends, this requires both Plotters and the backend crates depdens on a
same version of
plotters-backend crate. This crate (
plotters-backend) will enforce that any revision (means the last number in a version number)
won't contains breaking change - both on the Plotters side and backend side.
Plotters main crate is always importing the backend crate with version specification
plotters-backend = "^<major>.<minor>*".
It's highly recommended that all the external crates follows the same rule to import
plotters-backend depdendency, to avoid protential breaking
plotters-backend crates gets a revision update.
We also impose a versioning rule with
plotters and some backends:
The compatible main crate (
plotters) and this crate (
plotters-backend) are always use the same major and minor version number.
All the plotters main crate and second-party backends with version "x.y.*" should be compatible, and they should depens on the latest version of
The built-in rasterizers.
Text anchor attributes are used to properly position the text.
The color type that is used by all the backend
The error produced by a drawing backend.
Describes font family. This can be either a specific font family name, such as "arial", or a general font family class, such as "serif" and "sans-serif"
Describes the font style. Such as Italic, Oblique, etc.
Specifying text transformations
The style data for the backend drawing API
The trait that abstracts a style of a text.
The drawing backend trait, which implements the low-level drawing APIs.
This trait has a set of default implementation. And the minimal requirement of
implementing a drawing backend is implementing the
A coordinate in the pixel-based backend. The coordinate follows the framebuffer's convention, which defines the top-left point as (0, 0).