The kinds of content a movable can place, by type, and how each is created.
Remarks
A sheet creates a movable's content from its JSON by looking the content's type up here. The
built-in kinds (picture, chart, shape, slicer, the form controls) are registered when the SDK
loads; a host registers its own the same way, and from then on a workbook that carries that
type creates the host's content, saves it through its toJSON, and offers it to the UI under
the same type (registerMovableRenderer in @sheetxl/react).
A type nobody has registered still loads and saves: it becomes an unmodeled content that
carries its JSON as it was.
A kind can be registered with a loader instead (Lazy), so its implementation is fetched
only when a workbook first holds one, or ahead of use by LazyModules.prefetch from
@sheetxl/utils. Until it arrives the movable places a stand-in that is named, positioned and
saved as it was read; see IMovable.isContentLoaded.
The kinds of content a movable can place, by type, and how each is created.
Remarks
A sheet creates a movable's content from its JSON by looking the content's
typeup here. The built-in kinds (picture, chart, shape, slicer, the form controls) are registered when the SDK loads; a host registers its own the same way, and from then on a workbook that carries that type creates the host's content, saves it through itstoJSON, and offers it to the UI under the same type (registerMovableRendererin@sheetxl/react).A type nobody has registered still loads and saves: it becomes an unmodeled content that carries its JSON as it was.
A kind can be registered with a loader instead (Lazy), so its implementation is fetched only when a workbook first holds one, or ahead of use by
LazyModules.prefetchfrom@sheetxl/utils. Until it arrives the movable places a stand-in that is named, positioned and saved as it was read; see IMovable.isContentLoaded.