This documentation is currently available in Portuguese. English and other languages are on the way.
Concepts — Understanding CrossFly
The canonical explanation of the why behind CrossFly: architecture, component model, rendering pipeline, paint thread, layout and lifecycle.
The mental map of CrossFly — app → ui → core → gl → libGDX — and why this separation exists.
The unifying idea of CrossFly — only Component exists, and container = Component + Layout.
How a pixel reaches the screen — Paint → per-primitive renderers → OpenGL — and what batching is.
CrossFly's threading model — single-threaded on the paint thread, onUI, and on-demand render.
How CrossFly measures and positions — relative by default — and why this is the basis of responsiveness.
The appearance model — Skin is structure, Theme are semantic roles per mode — and runtime theme switching.
From bootstrap to component — Main, Window.onShow, and the onAdd(firstTime)/onRemove hooks.
CrossFly's state philosophy — no reactive binding, no DI, imperative + explicit invalidation.