Hi Cliff,

so in short: the Loader (a view component) is bound to a Mediator, not a proxy. Your proxy just holds the names of the assets, which the Mediator/Loader shall load.
That's fine. Thanks,

Matthias

With the word "asset" I mean a visual asset (as3/flashCS3 based swf). This asset has to be loaded on runtime, because it is too huge to load before my application starts. And I know, that this would probably best placed into a ViewComponent, so no PMVC tier is involved, BUT because this SWF consists of a few assets/classes, I saw it as some kind of data. And the laoding of this (visual) data could be the task of a AssetDataProxy. The AssetDataProxy could notify the PreloaderMediator while loading and the corresponding Mediators when all content is loaded.
Am I totaly wrong with this?

Of yourse I could put loading into something outside of pmvc, but loading assets is part of my application. ;-)

Hello,

I would like to know the best practice, when I have to load Assets on runtime.
Should I use a Proxy (Model) to organize the import of visual classes and then create Mediators (View) and connect these to the new loaded ViewComponents?

The examples so far have all their assets loaded before the application starts, but how to handle a step by step loading on runtime best with pureMVC?

Regards,
Matthias