Files
WoWee/docs
Kelsi 074d590fad feat(ui): opt-in FrameXML load, and document the widget system
Loads the original interface from its own manifest, in the order it states,
before any addon — because addons are written against a world where FrameXML has
already defined its frames and its several thousand functions.

Expect it to fail. It is an experiment, it wants the missing-API fallback on
beside it to get anywhere, and a half-loaded FrameXML sitting on top of the
client's own interface is not a state to be in by accident, so it is off unless
asked for through WOWEE_LOAD_FRAMEXML.

The docs also give the missing-API fallback a findable home, which it did not
have: it went in under a commit about click thresholds because I ran git add -A
after saying I would land it separately, and nothing in that message mentions
seventy-six lines of Lua engine. The history cannot be corrected without
rewriting what is already pushed, so this at least makes the feature
discoverable by someone who did not watch it happen.

Written down with it: why XML becomes Lua rather than widgets directly, that
anchors are constraints rather than positions, what the two switches cost, and
the gaps — fonts sized but not loaded, four frame types that lay out but do not
behave, left button only, and a texture cache that never evicts.
2026-08-01 12:57:42 -07:00
..