|
Hi everyone,
first of all - thank you for this great framework, and the lively discussion.
I'm new to PureMVC and currently reworking a flash app to benefit from it. My app uses different visual themes that can be swapped at runtime. Theme assets include CSS files, fonts and images which are also loaded at runtime when needed. Any number of view components might use (share) them... I feel the best way to handle these assets would be by loading and caching them with remote proxies.
Now, although this sounds clearly view related, i'm wondering wether my view mediators should take care of it -- or if the model would be a better place. After all, these theme assets are persistent data and not coupled to any particular view components.
...
One other thing regarding these remote proxies: is it ok (or perhaps common) to mix Proxy with Facade? I'd want to do something like this:
1. proxy is asked to load all assets for a specific theme
2. proxy delegates to 3 subproxies, each responsible for loading and caching different asset types (css, font, img)
3. subproxies send onLoadComplete events to proxy
4. proxy notifies the app about the theme being ready to use
5. views can now retrieve assets through the proxy
Well, maybe this isn't a proxy after all, but rather a facade in front of 3 proxies? Would it still be registered with the model?
Thanks a lot for any thoughts on this.
|
Show Posts
