Been thinking a lot about the architecture of this. Currently the AssetLoaderProxy’s clients (ie the classes that actually do the loading of the different types of data) are Commands that are triggered by Notifications given by the AssetLoaderProxy. But I think this is a case “its pureMVC, let’s use Notifications”. The same effect could be achieved by an abstract client class and a client factory, without the overhead of sending a Notification, and it would make adding new clients far easier.
I’ve also created a client for loading Flex Modules, and added functionality to extract class instances from loaded SWFs.
I’m aiming for the end of July for my first alpha release of the AssetLoaderProxy and the LogProxy :-/ Hopefully I will have time, as it can be combined with my next job, which is a multimedia presentation tool to be implemented in pureMVC Flex and Air – YEY!
mmm… I guess I need to look at a FileStream client too. Best put that on the list.
Thinking some more, lets do away with a factory altogether. We can register the clients directly, they can be added and removed at run time.