API

This section is the high-level map of the SAMSON SDK. It does not replace the generated API reference. Instead, it helps you decide which library group to open first and which concepts to review before you dive into individual classes.

The SDK is organized into seven library groups. In practice, most extension developers move between these pages and the concept chapters such as SDK Organization, Data graph, Developing GUI, and Modeling and Simulation.

How to use this section

• Start with the library group that matches the problem you are solving.
• Open the library page underneath it to find the main classes and macros to look up next.
• Use the generated API pages for signatures and detailed member-level behavior.

Library groups

• The Core Library Group: reflection, references, serialization, logging, containers, and undo infrastructure.
• The DataModel Library Group: documents, nodes, apps, controllers, quantities, and other data graph building blocks.
• The Facade Library Group: the SAMSON entry point used by extensions to access application-level services.
• The GUI Library Group: application GUI classes, editors, windows, widgets, settings, and render-side helpers.
• The IO Library Group: importer, exporter, and file-reader infrastructure.
• The Modeling Library Group: structural, visual, interaction, dynamical, and property models.
• The Simulation Library Group: simulators, state updaters, and neighbor-search components.

Suggested starting points

• Writing an app, editor, or tool window: start with DataModel, GUI, and Facade.
• Working with custom nodes or documents: start with DataModel and Core.
• Building file import/export support: start with IO, then check GUI for user-facing dialogs.
• Implementing models or simulations: start with Modeling and Simulation.

See also

• SDK Organization
• Fundamentals