|Need to cover some basics which you haven't mentioned which is always slightly scary
1.) I assume you are talking new OpenGL that is 3.0+ not old style OpenGL
Old style has the glBegin glEnd etc the new style you can't do anything without a shader and you drag all the function implementation pointers yourself.
2.) On the new OpenGL, GLM is one library you can use for matrix and maths stuff that ultimately ends up out on the shader in a sort of MVC setup.
3.) PureMVC is aimed at breaking the processing up via a predictable framework generally so you can thread it or use multicores.
I take it your current code is a linear application so not something you can port easily to PureMVC you need to design it differently from the start.
The next problem is PureMVC can be problematic in some situations like you have a client app interface sitting on a server which really has all the models. So the model view is handed to the client via the server. Lots of CAD programs and network games work that way and PureMVC is limited to what it can do. You can sort of shim it but you lose much of the effect and there are better techniques.
So can you start with a basic what OpenGL version and how your app is setup (models are where?) and when you say scale up what do you mean (more users, more processor cores)?
In vino veritas
modified 30-Jul-17 9:59am.