Something went wrong

Thank you for being patient! We're working hard on resolving the issue

Why a Standalone Library - Lona Docs Log in

Why a Standalone Library

@tento-lona/sheets carries the row taxonomy, render pipeline, and backend interface — but it has zero dependency on @tento-lona. This split is intentional.

Dependency direction

@tento-core       (data structures, algorithms — dep-free utilities)
       ↑
@tento-lona/sheets      (data model + render pipeline — NO DOM, NO SDK client)
       ↑
@tento-lona           (SDK client: LonaSdk, RowClient, indices, prefs)
       ↑
@tento-lona/sheets-ui    (DOM platform impl: Sheet web component, plugins, gestures)
       ↑
lona-so            (application: app-specific UI, LonaApi, feature flags)

A consumer can pick the level it needs:

  • A test or fixture writer that round-trips wire data uses @tento-lona/sheets alone.
  • A renderer back-end (CLI, TUI, native canvas) consumes @tento-lona/sheets plus its own platform layer — no SDK client needed.
  • An app like lona-so opens an SDK client (@tento-lona) and composes the DOM front-end (@tento-lona/sheets-ui) on top.

What stays here

  • Identity — Sheet, SheetRow, RowKey, RowId, RowLocalId
  • Wire vocabulary — Dtype, CellEntry, CellValue, CellStyle, Cardinality, the canonical encodings (EVENT_V1, TASK_V1, WEATHER_V1, SLOT_V1)
  • Backends — Backend interface plus TestBackend, NormalizingBackend, CanonicalBackend, HttpBackend
  • Row-type registry — ROW_TYPE_SPECS, reconcileAttributes, resolveChildren, dataPresetToChildSpecs
  • Alias templates — ALIAS_TEMPLATES, expandAliasInstance, resolveAliasActiveLayout, the built-in alias factories
  • System rows — buildSystemRows, HEADERS_STATIC, FOOTERS_STATIC
  • Render pipeline — PerTypeSpec, RenderScene, buildScene, diffScene, TreeWatcher, LayoutEngine, RenderPlan, plugin data providers, TuiReconciler
  • Pure chart data — LinearYScaler, castData, formatValue, GraphData, ChartPointerStore, DiscreteConvolution

What stays in @tento-lona

  • SDK runtime — LonaSdk.Client, RowClient, CellHandle, RangeCellHandle, RowsAccessor
  • Domain clients — CalendarClient, EventsClient, TasksClient, ChatAgentClient, SchedulingLinksClient, SyncClient
  • Preferences — PreferencesClient and the per-feature stores
  • Indices — EventsIndex, TasksIndex, DataIndex, RegressionIndex (cache-backed accessors over the canonical cells the rows-side Sheet exposes)
  • View model — SheetViewModel, RowTree, buildRowTree

If a name clearly belongs to "data model" or "render pipeline" but sits in @tento-lona, it's a migration candidate — open an issue.

See also