Skip to content

Component catalogue

Choose a portable control or layout primitive and check its current API.

On this page

Components provide behavior and minimal overridable defaults. You supply the application design with CSS-like or Rust styles. Native bindings implement primitives; your application does not import engine widget types.

Portable catalogue

ComponentUse it toEngines
ButtonTrigger an action from a labeled control.All three
InputEdit a controlled single-line string.All three
TextAreaEdit multiline text with wrapping and caret scrolling.All three
CheckboxControl a labeled boolean choice.All three
SwitchTurn a labeled setting on or off.All three
ProgressShow a finite amount of completed work.All three
MeterShow a finite measurement within explicit bounds.All three
TextDisplay text with shared shaping and glyph pixels.All three
BadgeDisplay a short status label.All three
CardGroup related child content in a surface.All three
SeparatorDraw a decorative divider.All three
BoxCreate a physical vertical container.All three
ContainerConstrain and center a reading or application column.All three
RowArrange child nodes horizontally.All three
ColumnArrange child nodes vertically.All three
CenterCenter a group within available free space.All three
SpacerConsume free main-axis space in a Row or Column.All three
FlexChoose a flexible layout direction and wrapping policy.All three
GridArrange direct children in equal-width columns.All three
AspectRatioSize a container around a positive width-to-height ratio.All three
ScrollAreaClip and scroll bounded child content.All three

TextInput is an authored alias for Input. All three playgrounds show these 21 component pages with working controls and shared fonts. Each component Usage section contains a complete src/App.iru you can paste into the scaffold, including state, handlers and scoped styles. Follow the engine/feature notes for egui-only controls and Markdown.

Additional components

Portable availability does not certify full screen-reader, IME or keyboard parity on every OS. Read alpha status, and test your application's target platform.

Source and appearance

Framework component constructors live in packages/inrux-components/src/components/. Application examples and the documentation-style theme live in playground/<engine>/src/. Use the exact CSS subset and public parts before assuming arbitrary native internals can be styled.

Each component page groups its contract under API Reference, with Props (type, default and description), common styling/identity props, and Emits (event, payload and description). A component with no emitted events says so explicitly.

Inrux · Built with Nuxt Content, IPEX, and Akaza UI.