Skip to content

feat: decouple engine from renderer - #98

Open
Satvik-Singh192 wants to merge 1 commit into
devfrom
chore/decouple_engine_renderer
Open

feat: decouple engine from renderer#98
Satvik-Singh192 wants to merge 1 commit into
devfrom
chore/decouple_engine_renderer

Conversation

@Satvik-Singh192

Copy link
Copy Markdown
Owner

Description

Refactored the project to decouple the physics engine from the desktop renderer and laid the foundation for WebAssembly support.

Changes Made

  • Refactored the engine into a standalone AetherEngine library.
  • Introduced AetherAPI as the public interface between the engine and renderer.
  • Updated the desktop renderer to use AetherAPI instead of directly accessing PhysicsWorld.
  • Added a separate WebAssembly build target using Emscripten.
  • Reorganized the CMake build to support both Desktop and WASM targets.

Implementation Details

  • Introduced AetherAPI and RenderBody to provide a clean abstraction over the engine.
  • Separated engine and renderer dependencies to make the engine platform-independent.
  • Added an initial WASM entry point and verified that the engine successfully compiles to WebAssembly.
  • Preserved desktop functionality while preparing the codebase for future web-based rendering.

Checklist

Type:

  • Bug Fix
  • Feature
  • Chore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant