How slyzerr/orvexa-engine works
Orvexa is an early-stage C++ 2D game engine; the README describes an ECS architecture, but the sampled runtime does not yet expose ECS behavior. The visible user-to-result path is program startup, runtime initialization, and a window event/update loop. Input state and frame timing are runtime services; rendering is currently empty. File/text access and JSON parsing are present as standalone utilities, but no sampled runtime code connects them to the loop. The graph reflects shown calls and documented scope; it does not infer unsampled integrations.
Main entry points: Runtime.cpp Runtime loop · JsonParser.cpp JSON parser · main.cpp Program entry · Inputs.cpp Input state
Components 10
Engine runtime
- Program entry
Project Engine/main.cpp - Runtime loop
Project Engine/Runtime.cpp - Window events
Project Engine/Window.cpp - Input state
Project Engine/Inputs.cpp - Frame timing
Project Engine/Time.cpp
Data utilities
- File access
Project Engine/FileSystem.cpp - JSON parser
Project Engine/JsonParser.cpp - JSON library
external/Json/json.hpp
Runtime support
- Logging
Project Engine/Logger.h
Other components
- Engine user
Connections 9
- Engine user → Program entry: starts
- Program entry → Runtime loop: initializes and runs
Project Engine/main.cpp - Runtime loop → Window events: creates, polls, closes
Project Engine/Runtime.cpp - Runtime loop → Input state: dispatches events
Project Engine/Runtime.cpp - Runtime loop → Frame timing: updates frame clock
Project Engine/Runtime.cpp - Runtime loop → Input state: queries input state
Project Engine/Runtime.cpp - Runtime loop → Logging: logs lifecycle and input
Project Engine/Runtime.cpp - JSON parser → Logging: logs parse results
Project Engine/JsonParser.cpp - JSON parser → JSON library: parses JSON