BusDK Update

bus-gx: the Go-to-WASM UI framework under every Bus portal ships v0.1.x

bus-gx is the early Go-to-WebAssembly UI framework used underneath BusDK portals. It owns the low-level GX render tree, source tooling, static compiler, and small browser mount runtime that portal UI layers build on.

The May release run from v0.1.5 through v0.1.11 moved the module from richer component markup into function callbacks, interactive intrinsic elements, DOM event wiring, runtime diagnostics, test helpers, and a browser-backed WASM app acceptance fixture.

May 16, 2026bus-gxGo WebAssemblyUI runtime

In Brief

TL;DR

bus-gx is BusDK's own early Go-to-WASM UI layer for portal interfaces.
The v0.1.x run added component children, callback props, interactive intrinsic elements, DOM callback wiring, a small mount runtime, diagnostics, and test helpers.
v0.1.11 release evidence covered an editor app that accepts input, handles submit and click callbacks, changes Go state, and rerenders the DOM in browser-backed tests.

A typical module check stays close to ordinary Go and the BusDK dispatcher:

$ bus gx version
bus-gx v0.1.11
$ bus gx compile editor.gx --output editor.go   # Go UI source generated

The important change is architectural: the platform UI foundation is written in Go and compiled to WebAssembly. Portal code can use GX component markup and ordinary Go functions while the runtime mounts a root, renders the returned node tree into the browser DOM, wires callbacks, and rerenders after state changes.

The module is still early. The 0.1.x label matters because callback names, runtime helpers, and acceptance fixtures were still being shaped in public module evidence. That maturity level is useful for BusDK because it keeps the framework small enough to evolve while portals start depending on the same low-level render and WASM boundary.

By v0.1.11, the module evidence covered a complete WASM app fixture: compiled GX component body markup, input callbacks, submit and click callbacks, Go state changes, DOM rerendering, and browser-backed tests. See docs.busdk.com for BusDK module documentation.