verso-tile 0.0.1

Tile-rendering-surface management for the Mere browser — Verso brand layer that places engine output into GraphTree tiles.
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

//! # Verso-Tile
//!
//! Tile-rendering-surface management for the
//! [`mere`](https://crates.io/crates/mere) browser. *Verso* is the brand-level
//! name (Latin *verso*: the back side of a printed leaf, the page that catches
//! the impression); `verso-tile` is the crate that owns the rendering surfaces
//! themselves — receiving output from engines (via the
//! [`inker`](https://crates.io/crates/inker) controller) and placing those
//! renderings into tile slots in the GraphTree.
//!
//! In the printing-press metaphor that organizes Mere's architecture:
//! engines produce ink, the inker pairs each ink to its content, the
//! [`platen`](https://crates.io/crates/platen) presses the inked content,
//! and `verso-tile` is the surface that receives the impression.
//!
//! ## Status
//!
//! Pre-1.0. This 0.0.x release reserves the crate name and documents intent;
//! implementation is in progress within the
//! [Mere workspace](https://crates.io/crates/mere).

#![doc(html_root_url = "https://docs.rs/verso-tile/0.0.1")]

/// Crate version.
pub const VERSION: &str = env!("CARGO_PKG_VERSION");

/// Lifecycle stage marker.
pub const STAGE: &str = "pre-alpha";