Lines Matching full:backend

2 …The Plotters backend API crate. This is a part of Plotters, the Rust drawing and plotting library,…
5 …This is the crate that used as the connector between Plotters and different backend crates. Since …
9 …To use a external backend, just depends on both the Plotters main crate and the third-party backen…
11   # Notes for implementing Backend for Plotters
13 …To create a new Plotters backend, this crate should be imported to the crate and the trait [Drawin…
14 …be implemented. It's highly recommended that the third-party backend uses `plotters-backend` by ve…
17 …If the backend only implements [DrawingBackend::draw_pixel](trait.DrawingBackend.html#tymethod.dra…
18 …used to give your backend ability of drawing different shapes. For those backend that supports adv…
19 …rated shape drawing, all the provided trait method can be overriden from the specific backend code.
21 …If your backend have text rendering ability, you may want to override the [DrawingBackend::estimat…
22 …the Plotters default text handling code may behaves differently from the backend in terms of text …
25 …Backend might render the image realtimely/animated, for example, a GTK backend for realtime displa…
26 …ed` and `present` method. The following figure illustrates how Plotters operates a drawing backend.
28 …tters want to draw. This function should initialize the backend for current frame, if the backend …
47 … the `DrawingBackend::present` is only called once manually, or from the Drop impl for the backend.
51 …and-play" schema to import backends, this requires both Plotters and the backend crates depdens on…
52 …same version of `plotters-backend` crate. This crate (`plotters-backend`) will enforce that any re…
53   won't contains breaking change - both on the Plotters side and backend side.
55 …Plotters main crate is always importing the backend crate with version specification `plotters-bac…
56 …d that all the external crates follows the same rule to import `plotters-backend` depdendency, to …
57   caused by `plotters-backend` crates gets a revision update.
60 …The compatible main crate (`plotters`) and this crate (`plotters-backend`) are always use the same…
61 …y.*" should be compatible, and they should depens on the latest version of `plotters-backend x.y.*`
75 /// A coordinate in the pixel-based backend. The coordinate follows the framebuffer's convention,
79 /// The error produced by a drawing backend.
82     /// A drawing backend error
91             DrawingErrorKind::DrawingError(e) => write!(fmt, "Drawing backend error: {}", e),  in fmt()
99 ///  The drawing backend trait, which implements the low-level drawing APIs.
101 ///  implementing a drawing backend is implementing the `draw_pixel` function.
103 ///  If the drawing backend supports vector graphics, the other drawing APIs should be
104 ///  override by the backend specific implementation. Otherwise, the default implementation
107     /// The error type reported by the backend
110     /// Get the dimension of the drawing backend in pixels
113     /// Ensure the backend is ready to draw
118     /// The backend may implement in the following way, when `ensure_prepared` is called
123     /// Draw a pixel on the drawing backend
124     /// - `point`: The backend pixel-based coordinate to draw
132     /// Draw a line on the drawing backend
145     /// Draw a rectangle on the drawing backend
160     /// Draw a path on the drawing backend
192     /// Draw a circle on the drawing backend
217     /// Draw a text on the drawing backend
264     /// Estimate the size of the horizontal text if rendered on this backend.
265     /// This is important because some of the backend may not have font ability.
266     /// Thus this allows those backend reports proper value rather than ask the
286     /// Blit a bitmap on to the backend.
292     /// this may not be the case. But for bitmap backend it's actually ok if we use the bitmap