Completemade from Musa CAD's own dataChecked against Musa CAD 0.8.0Verified
A survey of what is not yet implemented, grouped by theme, with the AutoCAD behaviour
each item is measured against. docs/COMMANDS.md is the per-command status table and
docs/TODO.md holds the fine-grained deferrals with rationale; this file is the map above
both, and each group below corresponds to a GitHub issue.
Status legend: P0 blocks ordinary drafting · P1 expected by a professional user ·
P2 completeness / parity.
The dimension model is strong (value computed from def points, never baked, one shared
compute_dim_geometry). What is missing is the editing surface AutoCAD gives.
Done: model, decoder seam, persistence, plot, viewport display (a textured-quad pipeline with a
per-definition texture cache), IMAGEATTACH / IMAGECLIP (rectangular and polygonal) / IMAGEFRAME,
the 8 MB embed limit, and DXF IMAGE/IMAGEDEF both ways (the writer now gives every record a
handle and carries CLASSES and the image dictionary).
Done (#4) — an opt-in to a converter installed on the host. ✅
Flathub submission
Manifest (org.musacad.MusaCAD, the reverse of musacad.org), metainfo and linter run prepared (packaging/flatpak/BUILD_FLATPAK.md); the PR asks for the home-filesystem exception. P2
macOS
The workflow publishes a .dmg and the command line works; the viewport needs OpenGL 4.5, which macOS does not have, and the app says so at startup — a Metal or GL 4.1 render path is the prerequisite (packaging/macos/BUILD_MACOS.md). P2
P0 first, and within P0 the dimension-editing pair leads, because a drafter hits
“I need this dimension to read <> H7” and “I need to move this text off the geometry”
on essentially every real sheet, and neither has a workaround that keeps the dimension
trustworthy. Tables come next (every fabrication sheet has a BOM or revision block), then
block authoring and paper space, which are larger structural pieces.