@skenora/babylon-editor
v0.1.3
Published
Babylon.js bridges between Skenora Editor, Runtime, and Flow.
Readme
@skenora/babylon-editor
Babylon.js adapters that connect Skenora's headless Editor, Runtime, and Flow packages.
pnpm add @skenora/babylon-editorExports include:
EditorRuntimeBridgefor projecting editor document changes;- bridge-local projection operation results and events for associating
operationId,projectionId,sourceRevision,changeId, and status; EditorFlowBridgefor editable Flow documents and explicit preview;RuntimeFlowControllerandcreateRuntimeFlowHostfor playback;EditorKeyboardControllerfor framework-neutral host shortcuts.
Renderer-only Flow playback is also available from the dedicated
@skenora/babylon-editor/runtime-flow entry so read-only applications can load
it only for documents that contain Flow graphs.
This is an integration package, not a product facade or UI component. Most
applications should start with @skenora/sdk.
EditorRuntimeBridge.flush() remains the compatibility API and now rejects
when a queued runtime projection fails. Hosts that need structured operation
tracking can use flushProjection() or projectCurrentDocument() and listen
to projectionEvents; each request can select strict or best-effort model
loading. Best-effort model failures are reported as partial with the failed
entity list. The association is intentionally bridge-local until the shared
runtime event contract can carry projection identifiers.
See the architecture guide.
