Expand description
The core: reading, capturing and driving a document. Inspecting, capturing and driving a document, with no window involved.
This is the core the two transports sit on. It answers a request against a
blitz-dom document and returns a response, and it knows nothing about
sockets, listeners, event loops or windows: crate::in_process calls it
directly and crate::server calls it across a socket, and neither is
visible from here.
It used to live in izumo, beside the Tauri runtime, which
meant that depending on it meant compiling Tauri. On Linux that means GTK:
system libraries pulled in to build a binary that never creates a window,
and a crate that would not compile there at all. The dependency edge was
wrong, not the platform. A runtime bridges Tauri to Blitz and owns a native
window; it is not where an inspection service lives.
Structs§
- Document
Capture - Reusable offscreen renderer for captures of one document.
Functions§
- capture_
document - Draw a standalone control document through the same CPU paint path used by runtime diagnostics.
- click_
agent_ node - focus_
agent_ node - hover_
agent_ node - Activate the node the caller selected, without asking hit-testing to select it a second time from a screen coordinate.
- inspect_
document - Read a document’s semantic tree.
- press_
agent_ key - snapshot_
document - Collect the same typed diagnostic snapshot from a standalone Blitz document that the windowed runtime exposes over its control socket.