How txfx/plus7 works
Project type and purpose
• From the README and file tree, Plus7 is an experimental, C++-based game engine.
• It is organized as a monorepo with a core task/pipeline system, multiple engine modules (graphics, input, UI, SDL application layer), third-party libraries, and sample usage.
File structure
• Top-level:
– CMakeLists.txt, build config, CI workflows
– Libs: bundled third-party dependencies (SDL2, ImGui, fmtlib)
– Plus7: engine code subdirectories
– Samples: example client code
• Plus7/Core: lightweight task scheduling and utilities
• Plus7/Modules:
– Gfx: abstract renderer interfaces + back-ends (Dummy, SDL+OpenGL)
– Inputs: platform-agnostic input APIs + SDL backend
– ImGui: wrapper for immediate-mode UI library
– SdlApp: application shell (window, main loop, context init)
• Dependencies flow inward: Modules depend on Core. Sample depends on SdlApp + other modules. Third-party libs feed modules.
README for additional insights
• CI status indicates standard CMake based continuous integration
Elements
• Clear labels: e.g., “Core: Task Pipeline,” “Gfx Module,” “SDL2”
– from SdlApp to SDL2 (init, loop)
– from Input module to SDL2 (poll)
– from Gfx module to glad/OpenGL, to SDL2 window
– from UI module into Gfx module
– from Sample app into SdlApp and Core