Overview
graphitepdf-render lowers layout output into typed render commands and also provides the concrete PDF backend used in the production crate-native pipeline.
Scope
graphitepdf-render contains:
RenderDocument,RenderPage, andRenderCommand- typed operations for text, images, SVG, fills, borders, transforms, forms, and debug overlays
RenderEnginefor lowering safe layout output into render commandsRendererSession,PdfRenderBackend, andrender_to_*helpers for end-to-end PDF generation
Installation
API Summary
| Category | Items |
|---|---|
| Render model | RenderDocument, RenderPage, RenderCommand, RenderContext |
| Operations | TextRenderOp, ImageRenderOp, SvgRenderOp, FillRectOp, BorderRenderOp, TransformRenderOp |
| Engines | RenderEngine, RendererSession, Renderer, PdfRenderBackend |
| Output helpers | render_to_bytes(), render_to_writer(), render_to_file() |
| Utilities | fit_object(), parse_color(), parse_transform(), parse_view_box(), resolve_svg_size() |
Example
use ;
use ;
use Pt;
use ;
use ;
Design Principles
- keep render commands typed and inspectable
- separate layout decisions from backend emission details
- make the production PDF path available without forcing callers through the root crate
- reuse
kitfor low-level PDF mechanics rather than re-implementing them here
Role In GraphitePDF
This crate is the canonical bridge from layout output to final PDF generation. It is the core of the production layout -> render -> kit -> PDF path.
License
MIT