Skip to content

Engine Orchestrator #109

Description

@Av3boy

We need a system that is responsible of all the coroutines within the engine. Such coroutines would be a window or a particle emitter handler. The orchestrator needs to asynchronously create those windows and emit particles with minimal blocking on the main thread, and on the drawing threads. Since the windows only need to process what to draw, everything else needs to be handled on a separate cpu thread to balance that load.

This also allows us to even further minimize what the engine does for those who want all the control but also simplifies creating new services for those who just might want to create games in the most straight forward way possible.

Activity

self-assigned this
on May 3, 2025
added a commit that references this issue on May 3, 2025
moved this to In Progress in A sharp planon May 3, 2025
added 5 commits that reference this issue on May 28, 2026
added a commit that references this issue on Jun 5, 2026
added 2 commits that reference this issue on Jun 28, 2026
moved this from In Progress to Done in A sharp planon Jun 28, 2026
closed this as completedby moving to Done in A sharp planon Jun 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

coreThe issue is related to the Core library.enhancementNew feature or requestmaintainability

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions