How the interface is rendered
KUI parses HTML into a DOM, resolves CSS, computes layout and builds a display list. A Skia backend presents the result in a native window. Compiler requirements are specified by the selected SDK package. Native code controls windows, documents, events and extensions.
Scripting and Web scope
Scripting uses optional embedded Lua. KUI does not run browser JavaScript applications or target the complete Web platform. Check the limitations of each CSS value and DOM behavior. Successful parsing alone does not establish complete support.
Choose a language binding
The C++ SDK uses the native public interface. The C SDK exposes a frozen C ABI, also used by Go and Rust. Bindings have separate version lines, so core version numbers alone do not establish package compatibility. The initial website release covers Windows x64.
Extensions and tools
DevTools inspects the DOM, styles, layout and performance; MCP exposes automation operations. Deploy 3D, editor and PDF extensions according to the package. DOM element extensions and media backends use different protocols.
Forms and native code
The settings project demonstrates the division between HTML/CSS and C++: markup defines navigation, fields and status, while native code reads live values, validates data and updates the interface. The teaching project includes source, build instructions and both language variants.

