The roadmap attempts to list the current goals, important dates, and other core information about the project.
TerraFX is still in the early stages of development. It is currently focusing on supporting Windows and Linux with aspirations to support macOS as well. For v1.0 to ship, the current minimum goals are to provide Audio, Graphics, Input, and Windowing layers on both systems. Additional components that are desired include a scene graph, transformations pipeline, and basic physics support.
The current status for each "component" is listed below. More details about the overal design can be found in the design folder.
Each component provides access to a different multimedia "subsystem". These components are brought together in the Application which exposes the various components and provides access to the "main loop".
The audio subsystem is being actively developed on Linux first. The initial support will be provided via PulseAudio. For Windows support, PulseAudio can be used but a more ideal system would utilize XAudio2 or the Windows Audio Session API (WASAPI).
The graphics subsystem is being actively developed on Windows and Linux simultaneously. It is currently utilizing Vulkan on both platforms and Direct3D 12 on Windows. Currently users can render a clear screen of any specified color. Adding support for rendering a set of primitives and meshes are next on the list.
The input subsystem has not started development but will provide support for both Keyboard and Mouse input at a minimum. This will likely utilize the underlying window messaging model for retrieving the input events.
A minimal windowing subsystem already exists. It utilizes Xlib on Linux and the Win32 "WinMsg" APIs on Windows. Currently this allows users to create barebones windows, perform basic operations such as resizing or moving, and manage their lifetimes. This subsystem includes an abstraction over the "message pump". Ideally, Linux would also allow utilizing XCB or Wayland, which are more "modern" APIs than Xlib.