Files
FreeCADWasmDev/docs/current/web-commandview-79ae27dac38bbd0b1358e4da-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

14 lines
1.9 KiB
Markdown

# Remaining implementation boundaries
Batch: `79ae27dac38bbd0b1358e4da`
The existing native `Std_ViewDock` route reached `core_view_command` but had no executable branch. The handler now validates dock/undock/fullscreen transitions using the desktop group command's toggle semantics, requires host acknowledgment (`previousViewMode`, `viewMode`, `mainFullscreen`), and persists the acknowledged mode in the document transaction. It does not claim that document state changes perform browser window operations.
This batch remains incomplete. The mounted active-view host and Web adapter still need to perform the window transition and supply the acknowledgment. `Std_ViewFullscreen` and `Std_ViewDockUndockFullscreen` have transition handling but must not be registered until that host path is connected. Actual browser failures must propagate without reporting native success.
Remaining selected behavior: Example1/2/3 must use their real scene implementations; FitSelection must fit native selected geometry; Home must apply the configured default orientation and fit; ViewGroup must dispatch its selected standard orientation; IssueCamPos must serialize the live camera and record the macro command; stereo commands must change the renderer using the requested stereo mode (including an explicit unsupported result where quad buffering is unavailable); LoadImage must open and display the selected image. No fixed outputs or implementation markers were added for these commands.
The four permitted supplemental source windows were used on WebViewCommands.h (1-60, 60-159, 160-259, 270-369). Further host and adapter patch anchors are needed to finish the integration. This source-window limit is not evidence that the business sources are absent.
No builds, tests, browser validation, benchmarks, acceptance runs, or historical reconciliation were performed. Incremental build/sync/route receipts remain owned by the outer pipeline.