PXML UI tutorials

These tutorials cover the complete PXML 1.0 UI authoring contract for developers building PCL.UI.Next interfaces. Every example keeps the build path visible and verifiable:

PXML source → validation → expansion and optimization → PXB → PCL.UI.Next Runtime

Learning path

1. Create your first UI: write, validate, compile, and inspect a PXB.
2. Syntax, nodes, and properties: namespaces, primitives, components, literals, and markup expressions.
3. Layout and sizing: Row, Column, Grid, Overlay, Absolute, Scroll, and constraints.
4. Bindings, commands, and events: pure state reads and explicit side-effect boundaries.
5. Conditions, lists, and virtualization: choose If, Switch, For, or VirtualList and maintain stable keys.
6. Components, templates, and slots: compile-time reuse without a runtime control object graph.
7. Styles, themes, and resources: PXSS, theme tokens, resources, and localization.
8. Motion, interaction, and accessibility: transitions, FLIP, behaviors, focus, and semantics.
9. Overlays, navigation, and NativeHost: lifecycle, barriers, pages, and platform controls.
10. Build, debug, and release: reproducible source-to-PXB integration.
11. Complete page example: combine the concepts into a download page.

Conventions

• XML snippets describe PXML 1.0 language semantics. The standalone compiler and target Runtime profile must both support the referenced nodes, properties, and ABI.
• bind reads state and performs pure computation; business side effects go through cmd.
• Components, templates, PXSS selectors, and resource names resolve at build time. Runtime keeps no XML DOM and does not discover controls through reflection.
• The compiler transforms build inputs. PCL.UI.Next Runtime owns windows, input, layout, animation, rendering, and platform NativeHost controls.

Follow the chapters in order for a complete path, or use the sidebar and search as a reference.