verso-tile 0.0.1

Tile-rendering-surface management for the Mere browser — Verso brand layer that places engine output into GraphTree tiles.
Documentation
  • Coverage
  • 100%
    3 out of 3 items documented0 out of 0 items with examples
  • Size
  • Source code size: 2.71 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 241.74 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 7s Average build duration of successful builds.
  • all releases: 6s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • crates.io
  • Dependencies
    • —
  • Versions
  • Owners
  • mark-ik

Verso-Tile

Tile-rendering-surface management for the 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 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 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.