Add professional controls with native code
Code editing, PDF viewing and 3D scenes have standalone extensions. Package the modules and resources your app uses. Editing source text in the editor does not change KUI’s Lua scripting model.
A pure C ABI for your own native capabilities
DOM element extensions use the kuiext_* host protocol with plugin information, initialization, element registration and shutdown entry points. Elements can implement measurement, painting and event behavior. Follow the current public headers and SDK lifecycle contract.
Extensions have deployment contracts
Build standalone extensions outside the SDK with find_package(Kui), checking ABI, architecture, runtimes, dependencies and assets. Media backends use the separate kui_media_* protocol. Include required assets such as the 3D material sidecar.
Something unclear?
Report an issue on this page →