AI_Assistant/cad-editor
Watch
1
0
Fork
You've already forked cad-editor
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
cad-editor/docs/issue-78-reply.md
Michael Flynn e46701456f Add plugin host architecture and Storm Sewer add-on package 
Generic plugin runtime (src/plugin/, HostSession, per-tab plugin_state, command router). QGIS-style add-on layout with plugin.toml and single PluginRegistration. Storm Sewer refactored as reference consumer with dispatch.rs, catchments, LandXML, headless tests (43 passing). Core update.rs decoupled from storm_sewer via CadCommand object-pick hooks. Docs: plugin-architecture.md, plugin-template, PR and issue-78 reply drafts.
2026-06-09 13:41:21 -04:00

2.2 KiB
Raw Blame History

Draft reply for Issue #78

Paste as a GitHub comment on https://github.com/HakanSeven12/OpenCADStudio/issues/78

@HakanSeven12 @schoeller — following up with a concrete architecture proposal and an implementation ready for review.

Proposal

I've drafted a QGIS-style add-on model on my fork:

Three layers: host core → add-on package (plugin.toml, ribbon, commands) → optional headless engine crate. Domain data lives on DWG entities (XDATA), not a proprietary project DB.

Phase 1 (in this PR): in-process plugins via inventory::submit!(PluginRegistration), HostSession API, per-document plugin state, command routing without editing commands.rs.

Phase 2: user install folder + dynamic .dll/.so with the same plugin.toml.

PR ready for review

I can open a PR against upstream with only the generic plugin host — no civil/hydraulics tab in core. Storm Sewer stays on a separate branch/repo as the reference consumer: feature/storm-sewer-module.

Re: script languages (@schoeller, #29)

Agree this shouldn't be either/or. Suggested sequencing:

  1. Native Rust add-ons + stable HostSession / ocs_plugin_api
  2. Python (or similar) as bindings over that same API — one extension surface, two authoring paths

Phase 1 defers embedded scripting until the native API is stable.

Questions for maintainers

  1. ocs_plugin_api as a workspace crate with semver — OK?
  2. Should the main repo ship zero discipline modules, or optional built-ins for dev?
  3. Priority: extract API crate (1b) vs dynamic loading (2)?

Happy to open the framework PR whenever timing works. Storm Sewer can follow as a separate installable add-on once the host lands.

— Michael