Ok, so I've read a lot about design patterns but have yet to really implement them. Reading = easy. Doing = hard. :0
My first question is, is it typical to create Composite MVC's (or nested MVC patterns?) throughout the application? To illustrate: Let's say an app has a pop-up window, which has a window box, a text area, and a button. Each of these implements the MVC pattern internally. The pop-up window itself implements MVC, and perhaps all three implement a composite interface. Would this architecture be typical and/or "correct"? The next question; if the above is correct then how do you connect them, especially in a Flash environment? Continuing the example, when the window-model is instantiated, it calls an attachmovie to WindowView, which is an MC in the library and has a corresponding WindowView class. So... ok now what? WindowModel instantiates new instances of Button and TextArea (calling their model-classes)? Is the Model the entry point for an MVC pattern? Then Button and TextArea take the WindowView inst as a param, and attach their views to it? This is where I really start to pull my hair out because there are so many options. I think the above would work, but I'm not really sure if that's using MVC correctly. Sorry for the super-long question, and thanks for your help!!! Best, Brent _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
