Looking at start up I noticed that there were several things that were happening that were outside of the scope of the GameboxApp class and better suited to be executed individually.
This is a more modular approach to the Post Setup Handlers that were being executed by having them in separate classes and individually registering. This creates an interface that could allow other game developers to execute code.
Right now I simply have all the argv, env and config being passed to each one of the setup handlers because I do not yet possess the understanding of how I would go about merging those parameters.
Looking at start up I noticed that there were several things that were happening that were outside of the scope of the GameboxApp class and better suited to be executed individually.
This is a more modular approach to the Post Setup Handlers that were being executed by having them in separate classes and individually registering. This creates an interface that could allow other game developers to execute code.
Right now I simply have all the argv, env and config being passed to each one of the setup handlers because I do not yet possess the understanding of how I would go about merging those parameters.