Documentation

Using the library

• Getting started: requirements, building and installing, versions, the build options, the model, a first screen, results, ids, defs and limits.
• Nodes and layout: the tree, flexbox, sizes, absolute placement, direction, the safe area and host content.
• Styling: layers, classes and states, conditions, tokens and themes, visual values, transitions and exits.
• Text: fonts, labels, spans, fallback and families.
• Text editing: fields, the caret and selection, input methods.
• Drawing: the draw list, content the program draws, glyphs, the reference renderer.
• Input: routing, pointers, focus and keys, gamepads, drags, drops and ranges.
• Scrolling, lists and popups.
• Accessibility: roles and names, updates and requests, the platform adapters.
• Maul Window: the glue to Maul Window, and the samples.
• Testing a program's interface without a window or a GPU.
• Licenses: what a program that ships the library carries.
• API reference, generated from the headers.

How it works

• Overview: the library's profile, the frame, and the host code it calls.
• Glossary.
• Node tree, Layout, Style, Draw list.
• Interaction and Scrolling and lists.
• Text, Glyphs and Text editing.
• Accessibility.
• Reference renderer, Window glue and The web.
• Maul conventions: the rules every Maul library follows.

Maintaining it

• Development: toolchain, presets, generated files, layout fixtures, fuzz findings, benchmarks and size.
• Test environments: lavapipe, the test backend, buses, platforms, browsers and screen readers.
• Test fonts: where each test font comes from, its license and its checksum.
• Checks: the local tiers, the tests and their labels, each CI job, fuzzing and the budgets.
• Release: how a version is made and published.