1. Home
  2. Docs
  3. Ecosystem

Ecosystem & Foundations

XenoAtom.Terminal.UI is built on a small stack of focused libraries. Together they provide:

  • a modern terminal API (output, input events, hosting)
  • ANSI/VT primitives (markup, styles, parsing)
  • a reactive retained-mode UI framework (visual tree, binding, layout, rendering)
XenoAtom.Terminal.UI
XenoAtom.Terminal.UI
Widgets, layout, rendering, and app model
Retained-mode UI framework for .NET terminal apps: visual tree, binding/state, layout, controls, scrolling, overlays.
Docs | GitHub
XenoAtom.Terminal
XenoAtom.Terminal
Terminal I/O, hosting, and input events
Terminal API and hosting layer: safe output, unified input events, inline live regions, fullscreen apps, and test backends.
Docs | GitHub
XenoAtom.Ansi
XenoAtom.Ansi
Markup, styles, and ANSI/VT parsing
ANSI/VT building blocks: style emission (SGR), markup parsing, tokenization, and ANSI-aware text utilities.
Docs | GitHub

Dependency chain (simplified)

At a high level:

  • XenoAtom.Terminal.UI depends on XenoAtom.Terminal and XenoAtom.Ansi
  • XenoAtom.Terminal depends on XenoAtom.Ansi

In other words:

XenoAtom.Terminal.UI -> XenoAtom.Terminal -> XenoAtom.Ansi

How they fit together

Library Role Depends on
XenoAtom.Terminal.UI UI widgets + layout + rendering XenoAtom.Terminal, XenoAtom.Ansi
XenoAtom.Terminal Terminal API (output/input/scopes/backends) XenoAtom.Ansi
XenoAtom.Ansi ANSI/VT primitives (markup, SGR, parsing) -

There is no dedicated website for XenoAtom.Terminal and XenoAtom.Ansi, so this documentation includes the most relevant parts you typically need when building apps with Terminal.UI.

  • XenoAtom.Terminal - the hosting and I/O foundation underneath Terminal.UI
  • XenoAtom.Ansi - markup syntax and ANSI primitives used by Terminal.UI (including the Markup control)
  • Markup - markup syntax reference and Terminal.UI semantic markup tokens