How seif-sallam/sfmlengine works
Main High-Level Components
• SFMLEngine (static library): the core engine
• Subsystems inside SFMLEngine:
– Entity-Component System (ECS)
– Scene/Level Manager (FSM)
– Rendering System
– Physics System (Box2D integration)
– GUI System (ImGui integration)
– Input Manager (Keyboard/Mouse)
– Resource Manager (Textures, Sounds, Fonts)
• External Dependencies: SFML, Box2D, ImGui, CMake/CPM
• Demo Applications (linking SFMLEngine): Sandbox, MazeGenerator, Asteroids
• Resource Repositories (rsc folders under each): settings, textures, sounds, etc.
• Build System: CMake + Makefiles producing a static engine library and executables
Relationships & Data Flows
• Demo Apps → link to → SFMLEngine library
• SFMLEngine → calls → SFML API for windowing, graphics, audio
• SFMLEngine → integrates → Box2D for physics bodies & collision
• SFMLEngine → embeds → ImGui for in-editor GUI
• Resource Manager → loads → assets from rsc folders
• Input Manager → polls → Keyboard/Mouse → dispatches events to ECS
• ECS Components (e.g. SpriteRenderer, RigidBody2D, Controller) → register with → Rendering System / Physics System
• Scene Manager → orchestrates → LevelScenes in each demo, swapping scenes via FSM
Architectural Patterns & Principles
• Modular, layered architecture: core engine layer + demo layer
• Entity-Component-System for behavioral composition
• Finite-State Machine to manage scenes/transitions
• Dependency inversion: engine subsystems depend on interfaces, not concrete platform APIs
• Resource centralization: single ResourceManager for all asset types