forked from 1b-agent/opencadstudio-upstream
Hakan SevenandClaude Opus 5.5
6d9365ea88
- An inverted clip's roundtrip record goes in the filter's extension dictionary through the codec's own API (ensure_extension_dictionary / xrecord / extension_dictionary_handle) instead of a scan of every object, which the renderer ran for each clipped reference. - Pin cadcodec 1c3be0c (the DXF writer now links a spatial filter's extension dictionary, so that record is not left unreferenced) and cadkernel deb529b; plugin crates and the Python plugin lock follow. - The XCLIP boundary preview stays f64. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Plugin registry
registry.json is the curated list of third-party plugins Open CAD Studio
offers in its Plugin Manager → marketplace. The app fetches it from this
repo's main branch at runtime, so adding an entry makes a plugin discoverable
to every user without an app update.
Add your plugin
Open a pull request adding one object to the array in
registry.json:
{
"repo": "your-account/your-plugin-repo",
"name": "Human-readable name",
"description": "One line describing what it does."
}
Requirements for the linked repo:
- Builds a
cdylibagainstocs_plugin_apiand exports the host symbols viaocs_plugin_api::export_plugin!. - Publishes per-platform binaries plus
plugin.tomlas GitHub Release assets (seecrates/ocs_example_pluginand its release workflow for a template). Asset names carry the platform, e.g.your.plugin-linux-x86_64.so,…-windows-x86_64.dll,…-macos-aarch64.dylib. plugin.tomldeclares anapi_versioncompatible with the host.
The host reads the release matching the user's platform, checks the API version, and installs it into the user's plugins folder.
Listing is curation, not endorsement or a security review. Installing a plugin runs its native code; users install at their own risk.