Architecture: Engine and Modules
[Under construction]
The system is structured as an engine class surrounded by a series of system modules. Each module manages other data and classes that the engine does not know about. For example, the engine starts the RendererFrontend but has no knowledge of the RendererBackend which the frontend manages.
This is an extension of the SystemModule interface. This is the main class for an application executable. If you look at the source code under Examples/ you will find that each example has 1 class that implements Application which defines the entry point for that example's executable.
The Application serves as the single point of contact between the engine and application space.
- Initialize all system modules in the correct order
- Run the main update loop
- Shut down all system modules in the correct order