VANILLA / ENGINE WORKBENCH

Control the Grid lifecycle.

Edit a revenue pipeline with the core Grid API. Switch the renderer, load rows from a paged source, and import or export a workbook. The host state shows each Grid generation.

Adapter: Vanilla
Scenario: 100,000 accounts
Owns: Grid lifecycle
Version: Sheetwrite 0.5.0

Grid ownershipInspect the renderer, source, or workbook.

Initializing WASM and 100,000 rows…

HOST-OWNED LIFECYCLE

Host state

Generation 1 · creating

Renderer: Requested: Main thread Active: starting
Datasource: Not mounted
Workbook: Revenue pipeline

Lifecycle checkEdit, rebuild, then remove the Grid.

1
Edit one value
Select B2, type a value in the formula bar, and commit it.
2
Switch its construction option
Rendering thread
Main threadWeb Worker
3
Destroy, then create
The stage action ends this generation and starts the next one from the same options.

Construction & debug controls

Public API in use

What this example demonstrates.

No mock controls or copied state. Every interaction above crosses the public adapter and Grid APIs.

01
Explicit lifecycle
createWorkbench and destroy() bound every generation — no listeners, chrome, or canvas survive teardown.
02
Construction-bound truth
Renderer and data path rebuild the grid and live in the URL; read-only flips on the running instance.
03
Host-owned paging
The page source, its latency, and its abort path are host code; allocation stats read back from the store.
04
Honest Worker fallback
A failed Worker boot emits renderer-fallback and keeps painting on the main thread — requested vs. active is always visible.