1.7 KiB
Web Parameter Dialogs
Implemented and published: Std_DlgPreferences and Std_DlgCustomize.
Receipt: web-parameter-dialogs-pipeline.json, two ready and zero missing.
No automated tests, browser validation, acceptance or benchmarks ran.
Both commands now reuse the existing native execute_parameter_editor and the
same PartBox/DocumentProbe owner-bound route as Std_DlgParameter:
- Preferences root:
User parameter:BaseApp/Preferences - Customize root:
User parameter:BaseApp/Workbench
The existing React parameter tree/table, group controls, typed value editor,
OPFS FCParam export/import and per-owner filenames are reused. No GUI-only
Qt dialog is invoked and no alternate parameter store is created. Native
ParamGet remains the source of truth.
Costs
| Step | Seconds |
|---|---|
| Capability registry reuse | 0.083 |
| Packet preparation | 0.735 |
| Formal native-owner pipeline | 60.975 |
| Pipeline artifact sync | 1.559 |
| Final frontend build | 4.159 |
| Frontend public asset sync | 2.680 |
The pipeline rebuilt the two existing document-owner artifacts under its build lock and exited successfully; no new WASM module was created. The final frontend build exited 0. The build was necessary because the standard command catalog and owner adapter changed; later parameter-only edits should reuse its artifact.
Remaining Scope
Global registry after this batch: 1347/1451 routed, 104 implementation-required. This is route/implementation accounting, not acceptance or parity. Console interactive interruption, remaining window commands and unconnected GUI dialog semantics remain separate. Automatic validation remains disabled by project policy; users validate through actual use.