htui 0.1.0

//! JavaScript scripting layer over the Boa engine.
//!
//! # Architecture
//!
//! A [`ScriptEngine`] owns a Boa [`Context`] plus a mutable DOM
//! ([`NodeArena`](crate::tdom::node::NodeArena)) that scripts manipulate
//! through browser-aligned bindings
//! (`document.getElementById`, `el.textContent`, `el.addEventListener`, …).
//!
//! The engine is a *side channel* like the rest of the event system: the
//! render thread still owns layout/paint, but when JS mutates the DOM the
//! engine reports a dirty flag and the input loop forwards the live arena to
//! the render thread via [`RenderCmd::RenderArena`](crate::tui::graph_api::RenderCmd::RenderArena)
//! — no HTML re-parse needed.
//!
//! # Event model
//!
//! `on*` attribute bodies are compiled to `function (event) { body }` at
//! startup (browser semantics: a bare identifier only evaluates, it never
//! calls). `addEventListener(type, fn)` registers JS functions on the JS side
//! (GC-safe). Dispatch walks the hit region's ancestor path target-first,
//! firing each element's listeners with a DOM-style `Event` object
//! (`target`, `currentTarget`, `x`, `y`, `stopPropagation()`).
//!
//! # Host functions
//!
//! Entries of [`EventBindings::host`](crate::events::EventBindings::host)
//! become JS globals callable from scripts;
//! they can push [`RenderCmd`](crate::tui::graph_api::RenderCmd)s and return
//! values. See [`host`].

mod bindings;
mod dom;
mod engine;
mod event_loop;
mod host;
mod msg;
mod state;

pub mod convert;

pub use convert::{FromJs, HostError, IntoJs, JsObjectBuilder};
pub use engine::ScriptEngine;
pub use host::{HostCtx, HostFn, host_fn};
pub use msg::{
    ScriptDirty, ScriptEvent, ScriptMsg, ScriptResponse, apply_message, run_script_thread,
};
pub(crate) use state::{ENGINE_STATE, ScriptState, TimerEntry};

use state::{EngineBuildError, EngineParts};