Thanks Cliff.  I'm coming from what Flex might people call a Flash/Agile builder perspective, and am slowly getting this more comp-sci approach. 

I suppose my problem lies in that I'm completely delaying the View commands until my model data is loaded and parsed.  Instead, I think I need to be commencing with the View stuff, but like you said, sort of make it wait until I can send another command to populate/draw the components.

I really hated pureMVC when we were first tasked to build with it (and the learning curve is steep, believe you me), but I'm seeing the structural efficiencies that on a larger scale would help track problems down and allow for changes.  I'll post again if I fall into a pot hole with the approach.

Hi all-  I'm trying to delay my ViewPreparation, to have it wait until the ModelPreparation is complete.  Since the ViewPrep command is no longer called from the Facade.startup(app) step, I'm wondering how to get an object variable of the app itself to a command not called directly by the facade.  This probably makes no sense, but it's a really simple notion in my mind: to have some simple way of returning the app itself as a variable, to be able to prepare the view outside of the facade.startup(app) methodology.

Thanks!

In order to reduce clutter, I have an issue making a preloader as well using Flash and pureMVC.  I've made an XmlProxy proxy, (the xml part isn't important really, you'll see why in a sec).  It uses BulkLoader to load a file.  That works fine.  Once the loading is complete I can use the data. 

My question is how to relay the progress info to the view- normally it'd be an event that fires when load progress changes- 10%, 14%, 29%, and so on.  Would I send a notification out for this?  Or is that overkill and there is a simpler way?  Or am I approaching it entirely the wrong way?  Having a progress notification would be handy for various display uses from one source.

Thanks!