I've been following this thread for the last few days and I finally got my account approved, yeah
In the first place I should say, that my post will not answer any of the questions here, instead I will ask some questions regarding the same topic. If someone thinks this is the wrong place for that, let me know so I can create a new thread for this.
I am also considering PureMVC for my next PV3D project and have been asking myself how the abstraction would work. Unfortunately Tipz already had an idea, so I would really love to know how that would work.
I just couldn't solve the question how I would seperate the PV3D "scene" from my objects.
In my application I will have an overview of different objects, which you can select. Lets say these are different categories.
Depending on which category you clicked, a new scene, the innerview, would appear. In this innerview I'd also have different objects which can be clicked. Doing that would show a detailed view of that object, but staying in the innerview.
I would seperate all the innerviews in individual swfs. Which would obviously lead to the MultiCore version of pmvc and the module-approach you've been talking about.
I just don't seem to unterstand how the overview and the innerview would be combined and how I would apply the MVC-pattern on the PV3D-structure.
Based on your ideas I would create a module for the overview, having it's own facade and his own pv3d-objects (scene, renderer, etc.) and a module for each innerview.
Should I create a Mediator for the "3DView" which would include the scene/viewport/renderer/camera?
Would an object (e.g. a cube) be a VC with it's own Mediator?
Antoher big question is, would pmvc have a bad influence on my performance, considering that pv3d is very weak in that matter?
Hope my english is pretty much understandable and the questions don't seem as confused as I am