Board & Styling Preview
Desktop UI with the finish of the web, written in C# and drawn by the same engine as the grid: a layout grid like CSS grid, typed style sheets with a cascade, drawn controls — and any grid, chart or 3D view as a tile.
Preview Part of ArionUI Core, open source under Apache-2.0. It carries dashboards, cockpits, feeds and business forms — tabs, option groups, combo boxes, date and number fields, menus and validation are built. The API still moves between preview versions.
Board
A grid of tracks that places controls in cells. Columns and rows are fixed, content-sized or shares of the rest; columns can repeat as many times as fit and wrap tiles onto more rows (Track.AutoFit, CSS auto-fit). Tiles span rows and columns, gaps and padding keep the rhythm, and breakpoints — Board.When(minWidth, …) — change tracks, placement and style rules with the board's own width, like container queries.
- Scroll or fit. A page as tall as its content, or rows that share the window's height.
- Nesting. A board is a control: a form inside a dashboard, a row of figures inside a page.
- Feeds.
ItemsFromturns a list into cards of varying height; only the cards near the view exist and are measured. - Arranged by the user. Splitters between tracks (
Board.Splitters), tiles moved with the mouse (MovableTiles) and docked beside one another, at the edge or as tabs of a split area (Docking,Split), Ctrl+Z to take it back; the layout can be saved and restored with the Pro packageArionUI.Layout. - Bound to a view model.
board.Bind(viewModel, x => x.Name): aPropertyChangedfrom any thread repaints what changed, on the UI thread. - Virtualized. The top-level board is drawn in bands like a grid's rows. Its cost budgets are tests: a hover repaints the two tiles it leaves and enters, at 100 tiles as at 1,000.
Styling
Style sheets in C#, laid out like CSS. Rules select tiles and controls by type, class and state (Select.Type<Button>().Class("primary").Hover); the cascade weighs the origin first — theme, the control's own hints, the application's sheets, the tile's inline style — then specificity, then order. Colours and lengths come from theme tokens, so a page follows every theme switch, including high contrast. A change of state blends over a transition; reduce motion turns it off.
And the cascade explains itself: Board.Explain(control) lists every declaration that was weighed for a tile, the winner first — the Styles pane of a browser's developer tools, as an API.
Styling in the documentation →
Showcase scenes “Styling lab”, “Feed” and “Appearance”, Avalonia host, 0.1.0-preview.1, each in the light and the dark theme.
Controls
Button, text box, multi-line text area, check box, toggle switch, radio buttons and option groups, combo box (pick from a list, or type with suggestions), numeric up-down, date picker with a calendar, slider, tab control, menu bar with F10 and access keys, toolbar, context menus on any control, image, label, separator, drop-down button, a free drawing surface; stack panel, scroll panel and card as containers. Each is focusable where it should be, walks with Tab, has a screen-reader role and value, can carry a tooltip, and takes its look from the style sheets. A control with an error text shows the Invalid state and the message — set by the application or bound to INotifyDataErrorInfo.
Controls in the documentation →
Any view as a tile
ViewTile puts any ArionUI view on a board: a data grid that sorts, filters, edits and searches, a card wall, a tree, a pivot, a chart, a 3D scene. Each runs in a grid session of its own; its menus and panes open above the whole board. That is what sets a board apart from a page of controls: the dashboard's order table is the full grid, not a picture of one.
Many of them stay cheap together. The showcase scene “Charts under load” puts up to 48 live charts in tiles: a hover over a chart draws its guide line and point as a stamp over the kept picture instead of repainting the chart, a scroll draws only the strip that comes into view, and a live update repaints only the charts whose data changed. Charts are Pro modules; the board and its tiles are Core.
Outside a grid, on all three hosts
ArionControlSurface puts a tree of controls anywhere in a window — docked in a WinForms form, in a WPF panel, as an Avalonia window's content. On WinForms it draws on the CPU without a GL context of its own, so a form can carry many of them. The WinForms showcase is built from six of them plus grid controls; WinForms only lays out the panels.
Control surface in the documentation → · Modernise a WinForms or WPF app → · Replace a DataGridView without rewriting the form →
Recently built
The plan of 4 October 2026 named what a complete application UI and the modernisation of old WinForms and WPF apps still needed. All of it is built — in preview, like the rest of Board & Styling.
Built Built since the plan of 4 October 2026
- The WinForms host as a NuGet package A WinForms team adds one package and tries ArionUI in its own form, without building anything from source.
- DataTable and DataView as live sources, columns generated from the table Most old forms hold their data in a DataTable; the grid sees its inserts, deletes and edits and types its columns from the schema.
- BindingSource support, with its position kept in step with the grid's current row Forms built in the designer navigate through a BindingSource; text boxes and navigators bound to it keep working next to the grid.
- Validation from the DataTable, IDataErrorInfo and INotifyDataErrorInfo as a ready edit policy Rules an application already has refuse or mark a wrong value in the grid, without a second validation layer.
- View-model binding for board controls board.Bind(viewModel, x => x.Property): a PropertyChanged on any thread repaints only what changed, on the UI thread.
- A theme from the system colours and the form's font, and one that follows Windows An ArionUI island in an old window looks like it belongs there, high-contrast schemes included.
- Lists of objects as a WinForms DataSource: BindingList<T> and List<T>, directly or through a BindingSource Forms that bind business objects instead of a DataTable swap the grid the same way; a BindingList reports its changes by itself.
- A WinForms sample: one form with a DataTable, from before to after in three steps A migration path is believable when you can open every step and compare.
- Tab control Almost every business form groups its fields on tabs.
- Radio buttons and option groups An exclusive choice with arrow keys and the right screen-reader role, not faked with check boxes.
- A combo box: a value with type-ahead, or free text with suggestions A form field needs a value it holds and a list you can type into.
- Multi-line text box Notes, comments and addresses do not fit on one line.
- Numeric up-down and date picker The editors the grid has in its cells, now as form fields, with formats and masks from the culture.
- Menu bar, toolbar and context menus on controls A window needs a menu bar at its top edge, with F10 and access keys, and a context menu on any control.
- Image control Logos, photos and icons, decoded once instead of on every frame.
- Tooltips on controls A button with only an icon needs a tooltip to explain itself.
- A validation state on controls: an error text and an Invalid state for style sheets A form shows which field is wrong and why, in the theme's colours, and a screen reader hears it.
- Draggable splitters between board tracks Users resize the regions of a working window; a double-click gives a track its size back, Ctrl+Z takes a drag back.
- Moving tiles with the mouse, and saving the board layout A dashboard users arrange themselves looks the same at the next start.
- Docking tiles beside another tile or at the board's edge Users build their own working window by dragging a panel where they want it, with a preview of the area it gets, Esc to cancel and Ctrl+Z to take it back.
- Split areas with tab groups, as in an IDE A board divided like Visual Studio's windows: panels share an area as tabs, switched with Ctrl+Tab, and a saved layout (Pro) keeps the tree.
- Charts in tiles that stay cheap under load A hover over a chart draws a stamp instead of repainting the chart, and a scroll draws only the newly shown strip, with dozens of live charts on one board.
Everything the plan of 4 October 2026 listed is built. The roadmap shows what comes now, next and later, what is built and what is not planned.
What stays out
- A native control inside a board tile. A tile shows what the engine draws; hosting a WinForms or WPF control inside one would leave the immediate-mode contract and the parity between the hosts. Old forms sit next to ArionUI, not inside it.
- Floating panels. Tiles dock inside their board and window; a panel torn out into a window of its own is not built.
- ActiveX for VB6, Delphi or Access. There is no ActiveX wrapper. A .NET host window could be reached from there, but that is a project of its own with an open outcome.
- Linux and macOS. Avalonia runs there, but ArionUI is developed and tested on Windows only so far.
- A visual designer. Boards, columns and style sheets are written in C#. What the cascade did is inspectable through Explain, but there is no drag-and-drop designer.
- A mirrored right-to-left layout. Bidirectional text inside a cell works; the grid and the board always lay out left to right.
- IME pre-edit. The candidate window sits at the caret, but text being composed is not shown inside the field.
Built and not planned across the whole product: Roadmap. Gaps of the grid itself: What it does not do yet.











