graphitepdf-document 0.4.0

Overview

graphitepdf-document provides compatibility-oriented Document, Node, TextNode, and ImageNode types that can be lowered into the canonical GraphitePDF layout and render pipeline.

Scope

graphitepdf-document contains:

• compatibility Document and Node authoring types
• text and image node helpers for content modeling
• conversion into graphitepdf_layout::Document, Page, and Node
• compatibility with renderer sessions through RendererDocumentSource

Installation

cargo add graphitepdf-document

API Summary

Example

use graphitepdf_document::{Document, Node, NodeKind, Style, TextNode};

fn main() {
    let title = Node::new(NodeKind::Text(TextNode::new("Hello GraphitePDF")), Style::default());
    let page = Node::new(NodeKind::View { children: vec![title] }, Style::default());

    let document = Document::new().add_page(page);
    let layout_document = document.to_layout_document();

    assert_eq!(layout_document.pages().len(), 1);
}

Design Principles

• preserve compatibility-friendly document authoring shapes
• keep lowering into the canonical crates explicit
• avoid duplicating layout or rendering policy inside the facade
• make it easy to bridge user-facing APIs into the crate-native pipeline

Role In GraphitePDF

This crate sits above the canonical pipeline as an adapter layer. It is useful when callers want a simpler document facade, but the real work still flows through layout, render, renderer, and kit.

License

MIT