How j-cowsert/so-so-engine works
Main Components
• So-so Engine Core (located primarily in the so-so directory):
• Core: This includes Application, Window, Input, Layer management, Logging, and other utility functions.
• Renderer: Contains implementations for rendering such as Mesh, Shader, Texture, Vertex Array, and abstraction of the rendering API.
• RendererAPI: Specifically your OpenGL abstraction (e.g., OpenGLRendererAPI, OpenGLBuffer, OpenGLShader, etc.).
• Events: Modules for application, key, and mouse events.
• Asset Management: Components like TextureImporter.
• ImGui Integration: Contains files to integrate ImGui for UI (ImGuiLayer, ImGuiBuild.cpp).
• Sandbox Application (located in the Sandbox directory):
• Demo Layers: EditorLayer, ShaderToyLayer, and TestLayer.
• Asset Resources: Models, Shaders, Textures that are used by the Sandbox demo.
• Miscellaneous: Helper headers like Model.h and Skybox.h, plus the SandboxApp.cpp implementation.
Relationships and Interactions
• The Engine Core provides the foundation for the application’s execution (Application / Window / Input and Event management).
• Layers are stacked within the engine allowing the Sandbox to add different application layers such as the Editor and test layers.
• The Asset Management subsystem feeds the Renderer with textures and models, which are stored in the Sandbox’s assets directory.
• ImGui integration facilitates a graphical interface over the engine’s core functionality.
Architectural Patterns & Design Principles
• Modularity: Components are clearly separated (Core, Renderer, Assets, Events, etc.).
• Abstraction: The use of RendererAPI (with OpenGL specifics) abstracts away low-level details from engine users.
• Layered Architecture: The engine leverages a layered system to structure different application aspects (rendering, UI, input, etc.).
• Extensibility: The Sandbox provides a practical demo to extend or test engine functionalities.