Roadmap 0.11, Add-on Library (Track AL)

AL.6 Add-on Library: "This file uses …"

  • Feature
  • Built · in the lab
  • CadCraft
  • BimCraft
  • ModelCraft
  • MarkupCraft
  • TakeoffCraft
  • CivilCraft
  • DetailCraft
  • PartCraft
  • SuperCad Studio

"This file uses …": drawings record the add-ons they need; the offer on open; pass-through until added

Spec docs/0.8-ADDON-LIBRARY-SPEC.md.

mounts-09 2026-11-06: Mounted and proved in the real page: CadCraft (CADCRAFT_ADDONS block), ModelCraft (usesAddons; tools/modelcraft-test/browser-al6.mjs 7/0), BimCraft (CadCraft_AddOns property set), CivilCraft (usesAddons; civil-mount browser al6). DetailCraft, TakeoffCraft and MarkupCraft keep no add-on data in their files (their add-ons are tools or rules), so there is nothing to stamp. PartCraft keeps add-on results in part.studies, whose keys (form, simulation, ...) are also used by built-in workspaces, so a key does not name an add-on: not stamped.

library-11 2026-11-20: unchanged. DetailCraft, TakeoffCraft and MarkupCraft keep no add-on data in their files; PartCraft is the open decision.

Waits on: PartCraft: which add-on data makes a file "use" an add-on: owner decision

Add a comment

Community comments

No comments yet

Add detail as we go: how you would use it, files or steps that show the problem, what other programs do. The team reads every comment.

Sign in or create a free account to add a comment.