[Ready] No raylib experiment

[Rover656]

This is a very early branch of an experiment to remove raylib from the workflow. This may seem like an unusual move, but with constant changes to raylib and bloat with 3d features, I have decided to try this out. Starting with a custom GL implementation, working into a renderer, then adding things like sound and resource loading. I have also tested this (in a testing/prototype project) on Desktop and UWP (Windows 10 and XB1), so this will be able to support all of our current target devices, with easy support for things like Android if necessary.

This will also allow us to ensure things like Audio work perfectly on these platforms and uses the native APIs (Like UWP audio) and also allows us to not have to bridge the gap between raylib and UWP (C <-> C++). This will be updated with progress.

TODO, not in order (From when I decided this is going to be used):

• [x] Gamepad
• [x] Finished renderer
• [x] Font loading
• [x] Audio loading
• [x] Audio playback (Using native APIs where possible??)
• [ ] Far better resource manager

[Rover656]

I have decided that this will be merged onto master after it is finished as UWP support is far greater than in raylib. This also allows us to add custom renderer features later down the line.

[Rover656]

All features that have currently been added have been tested and are working across both Desktop and UWP.

[Rover656]

A large number of bugs have been fixed, am going to be trying to fix the text renderer and also have plans to finish rewriting the resource manager.

[Rover656]

Resource manager will be rewritten sometime in master, this PR is prepping for merge.

[Rover656]

Final merge todo list:

• [x] Review OpenGL module
• [x] Add the rest of the shader attrib and uniform setters. Not exposing shaders to API's yet
• [x] Resource manager options for font defaults

[Rover656]

Also to note, managed to get a game through the Microsoft certification process for games. The engine is fit for UWP.