THREE.JS / FOUNDATIONS 319

The editor has its own document format.

TSL Graph persistence is application/editor state: executable material code plus graph layout. Exercise the official loader, storage keys, graph IDs, and failure boundaries without confusing it with native Node JSON.

Preparing TSL Graph fixture—

A trusted two-graph payload will be written through the official loader and applied by graph ID.

format
—
payload bytes
—
graph IDs
—
storage keys
—
code eval
—
layout state
—
selected graph
—
backend
—
frame samples
—
timing
NOT RUN
format contractwaiting

The official payload separates executable material code from visual graph state.

storage contractwaiting

TSLGraphLoader owns prefixed localStorage keys and overwrites imported codes/graphs.

trusted codewaiting

The loader evaluates imported material code; this fixture is trusted and deterministic.

backend boundarywaiting

Persistence is backend-independent; WebGL2 is exposed only through the explicit URL.

persistence event logwaiting

No graph events yet.

This lab snapshots and restores pre-existing local keys on release so the local study does not claim ownership of unrelated graph state.

Sources: TSL Graph example · TSL editor · Node · NodeLoader

LAB 319 / TSL GRAPH EDITOR PERSISTENCE