Files

T

History

triplestone 8e9ac74f0e refactor: 删除自维护 cadpy，模型总装改为自含 AssemblyHelper

模型实际只用 add/build 给部件打标签和颜色再组成 Compound，不需要
独立 Python 包。modular-case 与 smart-farm 各留一份项目内助手，
matx-case、engine-case、toast-inner-core 内联同签名实现；
packages/cadpy 与 packages/cadpy_metadata 删除。

2026-10-09 15:34:20 +09:00

cadgen

Release 0.7.19: fix what day one of PostHog telemetry showed (Windows mesh export, cad_file and cad_screenshot failures, crash noise, failure reasons) (#586 )

2026-10-09 01:35:24 +00:00

core

Release 0.7.19: fix what day one of PostHog telemetry showed (Windows mesh export, cad_file and cad_screenshot failures, crash noise, failure reasons) (#586 )

2026-10-09 01:35:24 +00:00

Release 0.7.19: fix what day one of PostHog telemetry showed (Windows mesh export, cad_file and cad_screenshot failures, crash noise, failure reasons) (#586 )

2026-10-09 01:35:24 +00:00

README.md

Web viewer: apps/packages layout, per-format renderers, fast selection on large models, tab-scoped state, lean CI (#450 )

2026-09-27 11:28:40 -07:00

README.md

Packages

Three shared packages support the applications in apps/docs and apps/web:

Directory	Identity	Responsibility
cadgen	Python distribution `cadgen`	CAD engine, store, CLI, build daemon, HTTP service and bundled runtime outputs
core	`@text-to-cad/core`	Framework-independent JS/TS geometry, rendering and explicit CAD service client
ui	`@text-to-cad/ui`	Complete shared FileViewer, injectable renderers, navigation, controls and styles

This migration is a pure refactor. All apps retain their existing UI, UX and functionality. Web and desktop both consume the same FileViewer; their adapters own browser/native services and application state. Docs consumes core for its static CAD showcases.

Apps import compiled public package exports. UI may depend on core; core never depends on React or UI. Shared packages never import application source, and applications never import one another. The root npm workspace and lockfile own JavaScript installation; npm run build:packages builds core before UI.

The Python wheel assembles built Node/browser runtimes and the built web client. That build dependency does not let Python engine code reach into app source. The wheel works outside this repository, so its own Markdown must also stand alone; repository development instructions belong in CONTRIBUTING.md.