How suit is built: the three-tree architecture it shares with Flutter, the constraint-layout protocol that replaces flexbox, the input model that routes pointer and keyboard events into the render tree,…
How suit is built: the three-tree architecture it shares with Flutter, the
constraint-layout protocol that replaces flexbox, the input model that routes pointer and
keyboard events into the render tree, the motion system that animates them, and the one
rule for getting work from a background thread onto the UI.
Pages
Architecture— suit is one layer of a three-layer system, the same division of labour Flutter draws between its widgets, its elements, and its render objects. Two of those layers already exist…
Layout— suit lays out with the protocol Flutter and SwiftUI both adopted — two greenfield frameworks that independently rejected flexbox for the same idea:
Input— Input is the bridge from raw device events to the render tree’s handlers. The runtime polls SDL for mouse, wheel, and keyboard events and feeds them to a set of…
Motion— suit animates the same way it lays out and paints: through a small seam, driven by the runtime, testable off-device. There is no animation framework bolted on — motion is…
Threading— suit has one thread rule, and it is the same rule every UI toolkit arrives at: