I know there is probably no definite right or wrong answer here, and it depends on the type of project, but I'm curious to get your opinion, if you're experienced with the MVC pattern (not frameworks per se that use MVC, I know about, say, Commands in Cairngorm and have checked into the Pure MVC architecture with its use of Notifications [though I only partially understand the Façade - I do something similar I think in a class I call "MVC"]- just interested in your opinions of raw MVC development).
My question is, in practice, when programming with the MVC design pattern, I know the Model is usually completely decoupled from outside classes, but do you usually completely decouple all other classes like views and controllers as well, in favor of dispatching events? Therefore communication between MVC classes are triggered completely by events (seems logical, but its also a heck of a lot of event handling) or do you have some coupling going on (i.e. the controller calls a method in the view telling it to change). Or do you follow what some frameworks do and use Command classes with lots of event handling going on? Trying to find a good mix, I can see advantages and disadvantages both ways. I'm doing a lot of event dispatching, but it seems a bit like overkill in some cases and harder to manage than just calling public methods. Interested in how you handle it when you use MVC pattern(s). Thanks, Jason Merrill Bank of America Global Learning Shared Services Solutions Development Monthly meetings on the Adobe Flash platform for rich media experiences - join the Bank of America Flash Platform Community _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
