valo-renderer 0.10.0

The wgpu core of valo: frame planner, encoder, pipelines, glyph atlases, caches
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

//! `valo-renderer` replays a recorded display list into wgpu render passes.
//!
//! Hosts normally use the `valo` crate's `Context`. This crate is the GPU core
//! that context wraps: it plans, encodes, and submits, and it owns only caches —
//! not application content. It talks to wgpu directly; there is no second GPU
//! abstraction.
//!
//! - [`HostBuffer`]: per-frame bump arena for transient uniforms and vertices.
//!   A 3-frame ring of persistent buffers means warm frames create nothing —
//!   the cost that matters most on wasm, where every create crosses into JS.
//! - [`PipelineCache`]: grow-only map of pipeline variants (format × blend × kind),
//!   the blend one the blend unit runs ([`PipelineBlend`], of a [`Blend`]).

mod contours;
mod device_request;
mod encoder;
mod frame;
mod glyphs;
mod gpu_timer;
mod host_buffer;
mod image_context;
mod images;
mod mips;
mod pipelines;
mod pixels;
mod planner;
mod pool;
mod ramps;
mod raster;
mod renderer;
mod report;
mod shader_abi;

pub use device_request::{request_device, FeatureLevel, NoDevice, Refusal, RefusedAdapter};
pub use glyphs::TextTiers;
pub use host_buffer::HostBuffer;
pub use image_context::ImageContext;
pub use images::{ImageDesc, ImageStore, IMAGE_FORMAT};
pub use pipelines::{
    AdvancedBlend, Blend, CompiledPipelines, Frag, PipelineBlend, PipelineCache, PipelineKey,
    PipelineKind, DEPTH_FORMAT, SAMPLE_COUNT,
};
pub use pixels::{AlphaType, ImageError, PixelBuffer, PixelFormat, PixelLayout};
pub use pool::TargetPool;
pub use renderer::{RenderStats, RenderTarget, RendererCore};
pub use report::{AtlasReport, MemoryReport, PoolReport, WgpuCounters};