ArionUI.Layout Pro

Namespace in the ArionUI.Layout package, 10 types.

Classes

ArionLayout: The complete persistable layout of a grid CONTROL: the view's GridLayout plus the user-changeable host state (frozen columns). Deliberately THEME-FREE: the theme is the app's/developer's choice, not layout state — an app that lets users pick a theme persists that itself (see the demo's wrapper).
ArionLayoutSerializer: JSON round-trip for ArionLayout — one place, one format.
GridApiLayoutExtensions: The grid level of persistence: frozen columns and rows, zoom, and embedded in it the state of the main view. Extension methods on the host-neutral facade; the view is passed in because the core knows no layout types.
GridLayout: A serialization-friendly snapshot of everything a user can change about a grid's layout at runtime: column order/width/visibility, sorting, grouping, all three filter kinds (text, operator, value checklist), active summaries and runtime conditional-formatting rules. Plain properties only, so any serializer (System.Text.Json, XML, ...) can round-trip it. Produced by GridView<T>.CaptureLayout, consumed by ApplyLayout. Persisted entries use application-owned string keys; integer element ids remain runtime implementation details and are never serialized.
GridLayout.ColumnLayout: One column's place in the layout, in display order.
GridLayout.RuleLayout: A runtime conditional-formatting rule (colors packed as ARGB, null = not set — a serializer round-trips uint? cleanly, Rgba less so).
GridLayout.SortLayout: One level of the multi-column sort, in priority order.
GridLayoutFile: Reading and writing a grid layout to a FILE — the "remember how the user left it" half of ArionLayoutSerializer.
GridLayoutPersistence: Layout persistence: the state a user set up (column widths, order, visibility, sort, grouping, filters with operator, summaries and conditional rules) as a serializable snapshot, and back. Built on the public surface only.

Enums

ArionLayoutParts: Which parts of the layout to persist — the app chooses what a "save layout" should include (columns, sorting, grouping, filters, …).