Data Ecosystem
This section describes the PlayMaker Data ecosystem from a developer and extension point of view.
Use these pages when you want to understand how schema, storage, UI binding, and UI actions fit together.
In This Section
| Page | Description |
|---|---|
| Schema and Storage | How DataDefinition, DataTable, and DataRecord work together. |
| UI Bindings and Hosts | How fields map to UI targets and how host components provide data. |
| UI Actions and Selection | How collection widgets process item actions and show selection state. |
| Planned Widgets and Extension Points | Reusable patterns for extending the data UI system. |
| Custom Data Visualizer Bindings | Add custom runtime bindings and Scene view drawers for data visualizers. |
Design Goals
The data system is designed to be:
- Schema-driven: all data is defined by
DataDefinition - GUID-stable: fields survive renames and refactors
- Host-driven: UI bindings never own schema
- Reusable: the same binding system works for tables, records, HUD, and widgets
- Extensible: new widgets and UI targets can plug in without modifying core code
Architectural Rules
These rules help the ecosystem scale without refactoring core systems:
- Schema is always owned by hosts.
- Bindings never own schema.
- UI targets never know the data source.
- UI actions never assume tables.
- All field identity uses GUIDs.