公开 API 参考Public API

快速判断一个能力应该从 ui 顶层还是子命名空间获取。Tell at a glance whether a capability lives at the ui top level or in a sub-namespace.

src/ui/ui.zig 就是完整的公开 API：应用只使用 ui.* 与 ui.<group>.*，破坏其中任何一个名字都算 API break。src/ui/ui.zig is the entire public API: apps use only ui.* and ui.<group>.*, and breaking any name in either counts as an API break.

const ui = @import("ui");
const zenit_app = @import("zenit_app");

// Tier 1: straight off ui
const title = try ui.text(cx, "Hello", .{});

// Tier 2: through the group
const theme = &ui.theme.dark;
const Router = ui.fx.Router;

Tier 1 · ui.X

每个应用都会用到的顶层名字，按用途分组。前五组覆盖大多数界面文件；最后一组面向自定义绘制与框架宿主。The top-level names every app reaches for, grouped by purpose. The first five groups cover most UI files; the last one is for custom drawing and framework hosts.

Tier 2 · ui.<group>.X

按关注点分组。需要超出基础能力时再使用。Grouped by concern. Reach for these when you need more than the basics.

组件的 props 与结果类型见组件站；图标清单见 Icon Gallery。ui.a11y 只用于平台运行时接线，应用作者不需要它——组件的无障碍信息写在节点的 A11yProps 上。Component props and result types are on the component site; the icon list is in the Icon Gallery. ui.a11y exists only for platform runtime wiring and isn’t for app authors — component accessibility lives in a node’s A11yProps.

zenit_app

zenit_app.App 是单窗口运行时助手，负责平台 / GPU / 字体初始化与事件循环；zenit_app.MultiWindowApp 管理多个独立原生窗口（上限 16 个，超出返回 error.TooManyWindows）。同一模块还导出 WindowConfig、MultiWindowConfig、FontConfig 与 ResourcePath。高级宿主可以使用更低层的接口，但普通应用应从这里开始。zenit_app.App is the single-window runtime helper — platform, GPU and font setup plus the event loop; zenit_app.MultiWindowApp manages several independent native windows (at most 16; beyond that you get error.TooManyWindows). The module also exports WindowConfig, MultiWindowConfig, FontConfig and ResourcePath. Advanced hosts can go lower, but ordinary apps should start here.

边界Boundary