How ionutcava/divide-framework works
Project type and purpose
• This is a C++‐based realtime graphics/game framework (“Divide-Framework”), comprising:
• An engine core (application loop, resource management, math, multithreading)
• Rendering backends (OpenGL/AZDO, experimental Vulkan)
• Subsystems: ECS, physics (PhysX/Jolt), AI, audio, input, networking, scripting (ChaiScript), UI (CEGUI, ImGui), terrain/vegetation, scene management, editor
• Tools: ProjectManager, editor UI, hot-reloading, unit tests
• It’s intended as a learning/experimental engine for prototyping and shipping small games.
File structure
• Top-level directories:
• Source/: contains all engine modules, organized by domain (Core, ECS, Rendering, Physics, AI, GUI, etc.)
• Assets/: audio, models, textures, scripts, shaders for demos
• Projects/, SaveData/, Screenshots/: sample scenes and run-time data
• ToolConfig/: IDE and debugger settings
• ThirdParty/: integrated libraries (EASTL, SDL, physics, ECS, ImGui, etc.)
• CMakeLists.txt & CMakePresets.json: build configuration
• Architectural patterns:
• Layered architecture: Platform → Core → Subsystems → Application
• Entity-Component-System (ECS) pattern
• Plugin-style render backends interchangeable at build or run time
• Modular subsystems (audio, physics, AI, etc.) communicating via well-defined interfaces
README for additional insights
• Confirms use of C++17/20, learning focus, OpenGL 4.6 AZDO, Vulkan 1.3
• Mentions editor and project manager UI, hot-reloading support
• Lists third-party dependencies and purpose