[ ] cache(name, value)
To store a uniform change in RAM but not in VRAM
[ ] flushCache()
To push stored changes into VRAM
[ ] clear()
To clear stored changes before entering VRAM
[ ] update(name, value)
There's something to be said about pluralization of the caching features for use in uniform blocks. Uniform blocks will likely be it's own class, though. Consider:
cache(std::vector<std::pair<char*,type>> values)
To store a number of uniform changes in RAM but not in VRAM
Create a class to handle the accessing of OpenGL Uniforms from the main program. To get a Uniform's location:
Needs control to understand the difference between:
This will make a good reference for all the access types