Grid Preview
One control, four ways to look at the same records, and a renderer whose frame costs the same for twenty columns as for a million, and for a thousand rows as for a hundred million.
What the table does
- Sort on header click, multi-sort with Shift, and a filter row under the header, plus value filters in a list.
- In-place editing with a self-drawn editor, typed editors and input masks; undo and redo of every edit.
- Search with match highlighting, a column chooser, column resize, auto-size and reorder.
- Card board and tree views of the same data, and master-detail rows.
- Keyboard navigation throughout, copy to the clipboard, and screen-reader support through UI Automation on all three hosts.
- Shaped text with font fallback, so CJK, Arabic, Indic scripts and emoji render correctly, and bidirectional text inside a cell.
- Dark and light themes built in, freely configurable.
Pro modules
Separate NuGet packages on top of the open engine, documented chapter by chapter — free during the preview, also commercially (see Pricing).
- Grouping from the column header, with group rows, aggregates and the group band —
ArionUI.Grouping - Pivot view with both axes collapsible —
ArionUI.Pivot - Conditional formatting with a rule manager —
ArionUI.Formatting - Charts, including 3D on the GPU —
ArionUI.Charts,ArionUI.Charts3D(see Chart) - Timeline view and planning matrix —
ArionUI.Timeline,ArionUI.Planning - Layout persistence across sessions —
ArionUI.Layout - Export to CSV, XLSX and PDF —
ArionUI.Export
The layers hold
Each layer names only what sits below it, and that boundary is enforced by tests rather than merely intended.
- ArionUI.Core
- The engine: virtualization, layout solver, scroll physics, interaction and the data sources. No UI framework — no Avalonia, WPF or Skia type appears anywhere in it.
- ArionUI.Presentation
- Views, column definitions, the cell composition model and theming. Framework-neutral.
- ArionUI.Grid
- The grid itself — panes, input wiring, the consumer API
ArionGridApi, accessibility. It draws only throughIRenderSurface. - ArionUI.Gpu and ArionUI.Rendering.Skia
- OpenGL ES 3.0 through a host-supplied loader, and the single Skia renderer shared by every host.
- ArionUI.Rendering.Avalonia, .Wpf and .WinForms
- Thin hosts: input mapping, a surface and a frame clock. Because the renderer is shared, all three draw the same frame.
Measured in both directions
| Frame cost while scrolling, WPF host | 20 × 1,000 | 20,000 × 1,000,000 | 1,000,000 × 100,000,000 |
|---|---|---|---|
| Vertically | 0.86 ms | 1.04 ms | 1.02 ms |
| Horizontally, far right | (too narrow) | 1.00 ms | 1.00 ms |
| Time to first picture | 1.0 s | 0.7 s | 5.4 s |
| Managed memory | 35 MB | 77 MB | 1.84 GB |
Columns × rows. Median of the best of three runs, maximized window (grid 1920 × 1129), Intel laptop GPU (i7-11800H, UHD Graphics), 60 Hz display, measured on 31 October 2026 on 0.1.0-preview.2. All three hosts held the display rate while scrolling. A million columns cost their setup once, not every frame.
Built for the GPU
ArionUI is built for the GPU: plain table cells go to it in one instanced draw call from the engine's own shader program, and the frame follows the visible area, not your data. Everything else is for emergencies and special cases, such as a remote session without a GPU: the Avalonia host then switches to a CPU path that repaints only the strip newly scrolled into view, and the WPF and WinForms hosts keep drawing through ANGLE, which can land on a software rasterizer. Either way it logs what it did. Hosting and rendering has the details, Performance what stays in your hands, and why virtualizing rows is not enough how this differs from a control per row.
What it does not do yet
Stated here rather than discovered later.
- It is an early preview: the API still moves, and breaking changes between preview versions are expected.
- No multi-touch gestures such as pinch; one finger works like a mouse.
- No mirrored right-to-left layout of the grid itself (bidirectional text inside a cell works).
- No IME pre-edit display.
- No floating panels: tiles dock beside one another and as tabs inside a board, but a panel cannot be torn out into a window of its own.
What was built most recently, and what is not planned: Roadmap. Whole windows around the grid — boards, style sheets, drawn controls — are on Board & Styling. Coming from WinForms: Replace a DataGridView without rewriting the form.
Licence and source
The engine is open source under the Apache License 2.0, patent grant included; the source and the issues are on GitHub. The Pro modules are NuGet packages without source, free during the preview.

