Game Engine 09/08/17 - Engine Services

While redesigning my Game Engine, I decided to separate different engine functions into different classes derived from a base class EngineModule. Modules can be located through the EngineLocator class, containing weak pointers to services provided.

At this point, I have the following modules & services:

• CoreModule - Manages Engine startup and termination;
• GlobalsModule - Manages Engine global variables (variant type variables, can be either strings, floats or booleans);
• LoggerModule - Logs the messages sent in the engine, depending on the implementation;
• CommandModule - Receives messages containing engine commands and executes them (such as sending messages & creating global variables, this class is primarly for debug purposes);
• ConsoleModule - Allows the user to execute engine commands and shows messages sent;
• FileSystem - Implements a layer of abstraction between OS calls to write and read from files and the engine;
• ResourcesModule - This one is where I'm working right now, manages engine resources, loading and unloading them as necessary.

All of these functions can be overriden without affecting the rest of the engine, making it way easier to implement crossplatform support.