How g3n/engine works
Main Components Organization
• Application Layer |
• Window | | GUI | | Scene | | Renderer | |
• Core Engine Layer |
• Graphics | | Audio | | Physics | | Camera | |
• Foundation Layer |
• Math32 | | GLS | | Geometry | | Material | |
Component Details and Relationships
Key relationships to highlight:
a. Core Components:
• Scene Graph → Node Management
• Renderer → OpenGL Abstraction (GLS)
• Audio System → OpenAL Integration
• Physics Engine → Collision Detection
b. Resource Management:
• Texture Loading
• Model Loading (GLTF, OBJ, COLLADA)
• Shader Management
• Audio Resource Handling
c. Cross-cutting Concerns:
• Event System
• Resource Management
• Memory Management
Platform-specific Components
• Platform Layer |
• Desktop (GLFW) |
• Browser (WebAssembly)|
• Audio Backends |
Detailed Component Breakdown
For each major component, show internal structure:
Graphics Pipeline:
• Geometry Data | --> | Shader System | --> | Frame Buffer |
Scene Graph:
• Scene Nodes | --> | Transformations | --> | Rendering |
Important Subsystems
GUI System:
• Widgets
• Layouts
• Event Handling
Audio System:
• Spatial Audio
• Format Support
• Audio Playback
Physics:
• Collision Detection
• Rigid Body Dynamics
• Constraints