subagent transcript

CONTEXT: FreeCAD 26.3 compiled to WebAssembly (emscripten, single-thread, ASYNCIFY, static Qt 6.11.1 + OCCT + Coin3D + CPython 3.14, NO dlopen/subprocess/threads). After a big push it now has 17 workbenches, numpy, Draft/TechDraw/Assembly all working. The 3D VIEWPORT RENDERS WELL (Coin3D -> WebGL via an offscreen FBO + QPainter blit). Toolbars/menus/tree are functional. THREE PROBLEM AREAS TO RESEARCH (be concrete, grep the real source + deploy, cite files): A) UNSTYLED UI (from a screenshot): the right "Tasks" panel (Gui::TaskView, shows "Start Part"/"New Body") has NO background — floating text on the 3D view. Context menus (right-click tree) are plain white, no hover highlight. NO hover states anywhere (buttons/menu items don't react on mouse-over). Font looks slightly oversized. This is the classic signature of FreeCAD's Qt STYLESHEET (.qss) + assets not being applied. FreeCAD ships stylesheets in src/Gui/Stylesheets/*.qss ("FreeCAD Dark.qss", "FreeCAD Light.qss", "Behave-*.qss") and the overlay/taskview qss; the active one is set by the preference MainWindow/StyleSheet and applied via qApp->setStyleSheet / Gui::Application. Icons/qss may be in a Qc qrc compiled into the wasm OR need FS packaging. B) The RENDER PERF hot path (from a profiler trace of a single mouse-wheel zoom = 96ms): dominated by Coin's IMMEDIATE-MODE GL emulation — emscripten's ffVertex/ffEnd/ffNormal3/ffColor4 (per-vertex glBegin/glVertex emulation) called from Coin scenegraph traversal (recursive wasm-function[15570]/[48370]), plus _glTexSubImage2D (~4ms, the FBO->texture blit) and _glReadPixels. deploy/index.html sets `COIN_VERTEX_ARRAYS=0` and `COIN_AUTO_CACHING=0` in Module.preRun ENV — these DISABLE Coin vertex arrays (forcing the slow immediate-mode path) and render caching. There are NO wasm debug symbols so wasm-function[N] can't be resolved. C) NEXT PARITY STAGES: (1) browser-reload PERSISTENCE is broken — IDBFS mount+hydrate work, but FreeCAD's user.cfg ParameterManager serializer is created in Application::bootstrapEarly()->LoadParameters() with a stale root path ("/user.cfg") before the real UserConfigPath is known; App.saveParameter() then writes to /user.cfg (or no-ops). An attempted fix re-pointed the serializer in LoadParameters()'s idempotent-guard using getUserConfigPath() but it did NOT work (user.cfg still not at /tmp/.config/FreeCAD/v26-3/). (2) CAM is blocked because pybind11 is absent from /opt/toolchains (CAM's area/tsp_solver need it). (3) BIM/Arch could partially load now that Draft+numpy exist (IFC needs ifcopenshell, but non-IFC Arch modeling may work). PATHS: FreeCAD source /home/magik6k/lcad-wasm/freecad-port/FreeCAD (git branch wasm-parity-push). wasm build tree /opt/toolchains/src/freecad-gui-build. deploy /home/magik6k/lcad-wasm/freecad-port/deploy (index.html + *.data + *.data.js — grep the .data.js manifests to see what's on the FS). Toolchain env: source /home/magik6k/lcad-wasm/env.sh. To check what's packaged: the .data.js files contain a JSON "files" manifest with "filename" paths. The base freecad.data mounts at /freecad (share at /freecad/share, modules at /freecad/Mod). getResourceDir()=/freecad/share/. Qt wasm plugin + qt.conf considerations apply. You are the planner. Four investigations covered UI styling, Qt platform, render perf, and next stages. Merge into ONE prioritized action plan for the main loop to execute. Rank actions by impact/effort, front-loading the no-rebuild quick wins (env flags, packaging, preference/boot.py changes) before rebuild-required work. Separate the biggest single UI fix (likely: package + apply the FreeCAD stylesheet, which fixes task-panel bg + context menu + hover in one go) and the biggest perf fix (likely: COIN_VERTEX_ARRAYS=1). De-dupe overlapping fixes between the styling and qt-platform dimensions. Flag which actions need a FreeCAD rebuild vs which are index.html/packaging/boot.py only. RESEARCH (JSON): [ { "area": "A) Unstyled UI — missing Qt stylesheet (task panel has no background, no hover, plain context menus, oversized font)", "rootCause": "The `MainWindow/StyleSheet` preference is EMPTY in the wasm user.cfg, so FreeCAD only applies the 20-line `defaults.qss` (which styles nothing but Gui::SplitButton) and never loads the real 2737-line theme `FreeCAD.qss`. Chain of evidence: (1) `StartupPostProcess::setStyleSheet()` at /home/magik6k/lcad-wasm/freecad-port/FreeCAD/src/Gui/StartupProcess.cpp:535-554 does `std::string style = hGrp->GetASCII(\"StyleSheet\")` with NO default → empty string on a fresh config, then calls `guiApp.setStyleSheet(\"\")`. (2) `Application::setStyleSheet()` at src/Gui/Application.cpp:2879-2984: when qssFile is empty it takes the else branch (line 2978/2984) and does `qApp->setStyleSheet(defaultStyleSheet)` where defaultStyleSheet is only `qss:defaults.qss`. (3) defaults.qss (/home/magik6k/lcad-wasm/freecad-port/FreeCAD/src/Gui/Stylesheets/defaults.qss) is 20 lines and only styles `Gui--SplitButton` — its own header comment says it intentionally does NOT style buttons/backgrounds. (4) All the actual UI styling — QMenu bg + `:hover`/`:selected`, and critically the Tasks panel background — lives ONLY in FreeCAD.qss: line 1581 `QSint--ActionGroup QFrame[class=\"content\"] { background-color: @DialogBackgroundColor; /* Task Panel background color */ }`, QMenu block at lines 501-560, hover states throughout. Because that file is never applied, the TaskView paints no background (floating text over the 3D view), menus are unstyled white, and there are no hover states — exactly the screenshot. This is NOT a packaging problem: the deploy manifest freecad.data.js already contains /freecad/share/Gui/Stylesheets/FreeCAD.qss, defaults.qss, parameters/FreeCAD {Light,Dark}.yaml, all images_classic/images_dark-light SVG/PNG, overlay qss, and the PreferencePacks — 516 Stylesheet entries. getResourceDir()=/freecad/share/ matches the qss search path registered at src/Gui/StartupProcess.cpp:142-149. The assets are …