Files
FreeCADWasmDev/docs/current/bim-7c4bddae6f3111efa987e5f7-boundaries.md
wangdequan 9a7c4f0335 Save FreeCAD Web workspace sources and user validation evidence
IFC native binding remains incomplete; preserve accurate test results.
2026-09-15 22:01:58 +08:00

1.9 KiB

BIM batch 7c4bddae6f3111efa987e5f7

Edits completed without tests, builds, sync, browser validation, benchmarks, or acceptance runs. The outer pipeline owns build/sync/route receipts.

Implemented

  • BIM_Windows now joins selected_document_helper in BimRuntimeProbe.cpp, allowing its registered document implementation to run without first importing and checking a desktop GUI command provider.
  • The mounted shell already forwards prepared BIM arguments to the dispatcher. In bim-desktop-adapter.ts, Windows requests with a nonempty changes object now default to apply; requests without changes default to read. Explicit actions are preserved. Invalid changes containers fail before dispatch.
  • The existing native Windows implementation reads actual document windows and materials, applies selected-object edits transactionally, and returns current values. Its width, height, label, tag, description, and material behavior was compared with the supplied desktop source; no replacement results were introduced.

Remaining boundaries

  • The packet contains existing registry entries for all seven selected commands despite reporting them as unregistered. No duplicate registrations or discovery markers were added. Runtime registration is unverified.
  • BIM_TDView, BIM_Text, BIM_TogglePanels, and BIM_Trash already appear in the document-helper routing excerpt. Their complete execution and UI behavior remain unverified in this edit-only turn.
  • The supplied Welcome helper invokes BIM_Welcome().Activated(). The IFC update helper invokes IFC_UpdateIOS().Activated(). Their complete Web host behavior is unresolved; this turn does not claim those GUI-dependent workflows are complete.
  • The four supplemental source windows are exhausted. Further source inspection must follow the next packet's named anchors and allowance. No validation receipt or business acceptance is claimed.