Dynamically created mediators and proxies?

[jon.opus]

I'm making a type of image editor with layers and the like that can move, scale and rotate. They will need to created or loaded, edited and saved. A problem I'm running into is that I don't know how to manage the layers.

The editor could be viewed in at least two ways:

1. "model data" that describes the "view components" that needs to be displayed.
2. "view components" that need to be recorded as "model data"

Ether way I feel like the two are tightly coupled. And It feels like I'll need to dynamically create mediators and proxies. Any sort of direction would be of great help.

[puremvc]

It sounds like yor model does need to track the layout metrics. That doesn't mean it should actually know about the view components that use those metrics for laying themselves out. Not that it is an specific guide for your implementation, but check out the AIR demos that use the DesktopCitizen utility, which persists the window metrics for your app. Also check out the HelloFlash demo which has some dynamically created mediators for self-directed sprites.   

Also search these forums for the topic 'Document-based app' where I responded with thoughts about the pairing of dynamically generated mediators and proxies that represent and manage documents.

-=Cliff>