0 Fork 0

forked from 1b-agent/opencadstudio-upstream

Files

T

Hakan SevenandClaude Opus 5.5 ac086def56 review(#1653 ): upstream pins, registered expression xdata, table apply refreshes sweeps

- Cargo: drop the fork patches; codec 8e93175, kernel 0665fc9, graph
  3b91e67 in every manifest and lock.
- A swept surface's expression link is written through set_entity_xdata,
  so OCS_SWEEP_EXPRESSION has its APPID record and the record its handle.
- Applying the whole named-parameter table also rebuilds the swept
  surfaces linked to expressions, not only a single-row edit.
- swept_surface_entity keeps its doc comment.
- The native-constraint tests find a scope's network through its own
  dictionary, where it is now stored.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-07 21:38:17 +03:00

opencad-python

review(#1653 ): upstream pins, registered expression xdata, table apply refreshes sweeps

2026-10-07 21:38:17 +03:00

README.md

docs(plugins): point to the example plugin repo and the API 4+ fingerprint

2026-09-28 20:53:51 +03:00

registry.json

registry: note Storm Sewer free/Pro split

2026-09-08 10:56:19 -04:00

README.md

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 cdylib against ocs_plugin_api and exports the host symbols via ocs_plugin_api::export_plugin!.
Publishes per-platform binaries plus plugin.toml as GitHub Release assets (see opencad-example-plugin and 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.toml declares an api_version compatible with the host (3 or newer). From API 4 on it must also carry the rustc_version and acadrust_source the library was built with; the host loads it only when both match its own build.

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.