0 Fork 0

forked from 1b-agent/opencadstudio-upstream

Files

T

Hakan SevenandClaude Opus 5.5 aa0b87108c feat(model): kernel a82f17d — MASSPROP from B-rep, curved OFFSET/FILLET

- Pins: codec 8189f83, kernel a82f17d, graph d3558bb (all manifests and
  the python plugin lock).
- MASSPROP reports volume, centroid, inertia, products, radii of
  gyration and principal moments of 3D solids and bodies from their
  B-rep (exact where analytic, else from a fine mesh).
- OFFSET of ellipses and splines through the kernel's curve offset.
- FILLET between circles, ellipses and splines through the kernel's
  curve-curve fillet, trimming arcs and open splines to the tangents.

The kernel bump brings the DWG ACIS audit fixes: slices, booleans and
press/pull on cones, slanted cylinder sections, survey coordinates,
spline walls and touching parts.

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

2026-10-09 08:25:09 +03:00

opencad-python

feat(model): kernel a82f17d — MASSPROP from B-rep, curved OFFSET/FILLET

2026-10-09 08:25:09 +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.