How embercraft/ember works
Project type and purpose
• Ember is a C++-based, cross-platform game engine (2D now, 3D soon), packaged as a library (Ember/) with an integrated Editor (Foundry/) and a Sandbox/demo application (Sandbox/).
• The README confirms core features (rendering, ECS, telemetry, UI), planned extensions (Vulkan, scripting, audio), and the build/run scripts.
File structure
• Top-level modules:
• Ember/ → the engine “core” (CMakeLists, src/, Vendor)
• Foundry/ → engine-powered game editor (EditorLayer, panels)
• Sandbox/ → demo application using the engine
• Scripts/ → Python tooling for build & codegen
• build/run scripts and config (run.sh, configure.sh, .gitmodules)
• Within Ember/:
• Core/ → Application, Window, Input, Logging, Timing, Layer stack
• Events/ → Event abstractions (application, keyboard, mouse)
• Math/ → vector/matrix utilities
• Renderer/ → abstract RendererAPI, 2D/Batch/Shader, Texture, Framebuffer, Cameras, Command interface
• ImGui/ → Editor UI integration layer
• Scene/ → ECS: Entity, Components, Scene graph, serialization
• Platform/ → OS‐binding (Linux Window/Input) and graphics backends (OpenGL)
• Debug/ → Instrumentor for profiling
• Foundry/ and Sandbox/ link against Ember as a static/shared library.
README for additional insights
• Confirms current focus (OpenGL, 2D, ECS, UI), upcoming modules (Vulkan/API, visual scripting).
• Build script arguments choose engine vs. sandbox startup, debug vs. release, GPU support.
Detail without over-splitting
• Do not list every header; instead, show logical subsystems and their interconnections.
• Editor and Sandbox apps are shown as “clients” of the Engine library.