Tag: rendering

One JSON Document, Live Data: Adding Data Bindings to oak-ui and Running It as a Vibe

oak-ui describes a whole app as one JSON document, but the document could only show data it already contained. Version 1.1 adds sources, bindings and commands against the app's own API: each distinct request fetched once per resolution pass, dependencies resolved in waves, paths that can't leave /api/, and API data that is never evaluated as code. Then we taught the vibe platform to serve app.oak.json as a page, fought a CSP over fonts, and shipped the first real oak-ui vibe to production.

Finishing Rise: The TUI Framework That Said It Was Done, and the App That Proved It Wasn't

Rise is our Bun-native terminal UI framework: typed-array screen buffer, zero dependencies. Its reports said complete. The type checker had 71 errors, four widgets drew garbage behind tests that asserted true === true, and the App class gave every widget the same hard-coded 10×3 layout constraints. This is how we finished it, and Rise Studio, the six-screen app we built on it to prove it.