Plug-ins and Extensions
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
A plug-in is an explicit extension with lifecycle and source contracts; the mere presence of native code is not a public extension guarantee.
Packages establish the reusable and versioned model assembly boundary. The LaTeX development guidance covers application configuration, package composition, class manifests, loading modes and conventions. A package definition is not the same as a running service or a deployment container.
Engineering rules
- Explicitly declare which packages compose an application.
- Review cross-package identity, dependencies and overrides.
- Keep naming and declaration formats aligned with the versioned grammar.
- Test package activation and ownership rather than assuming file presence implies activation.
Chapter outline (original LaTeX headings)
- Purpose of the Static Metadata Layer
- Two Complementary Readings of Metadata
- From Model Files to Static Metadata Objects
- TMetaDataObject as the Root Contract
- Source-Level Taxonomy of TMetaDataObject Descendants
- Functional Reading of the Taxonomy
LaTeX provenance
Primary chapter: Runtime/logiCells Runtime Programming with RadStudio/metadata-packages-and-plugins.tex.