A complete implementation of all systems Fluid needs to function, using Raylib as the base for communicating with the operating system. Use raylibStack to construct.
Implements Raylib support through Fluid's I/O system. Use raylibStack or raylibView to construct.
Use this enum to pick version of Raylib to use.
Identify image type by contents.
Convert a Raylib keyboard key to a KeyboardIO.Key code.
Convert a MouseIO.Button to a raylib.MouseButton.
raylibStack implements all I/O functionality needed for Fluid to function, using Raylib to read user input and present visuals on the screen.
raylibView implements some I/O functionality using the Raylib library, namely CanvasIO, KeyboardIO, MouseIO, ClipboardIO and ImageLoadIO.
Wrapper over NodeBuilder which enables specifying Raylib version.
Raylib connection layer for Fluid. This makes it possible to render Fluid apps and user interfaces through Raylib.
Use raylibStack for a complete implementation, and raylibView for a minimal one. The complete stack is recommended for most usages, as it bundles full mouse and keyboard support, while the chain node may be preferred for advanced usage and requires manual setup. See RaylibView's documentation for more information.
Note that because Raylib introduces breaking changes in every version, the current version of Raylib should be specified using raylibStack.v5_5(). Raylib 5.5 is currently the oldest version supported, and is the default in case no version is chosen explicitly.
Unlike fluid.backend.Raylib5Backend, this uses the new I/O system introduced in Fluid 0.8.0. This layer is recommended for new apps, but disabled by default.