Yup, you got it. To be even more specific... 1:N Views A) bind to data in the 1 ModelLocator (which contains 0:N Models/VO's) and B) broadcast 1:N Events to the 1 FrontController which maps Events to 1:N Commands which may create 0:N Delegates which trigger 0:N Services (using 1 ServiceLocator, if you have Services) the results are then passed from the Services back to the Delegates, which pass them back to the Commands, which then update the data (models/VO's) stored in the Model Locator.
Darren >From: "lostinrecursion" <[EMAIL PROTECTED]> >Reply-To: [email protected] >To: [email protected] >Subject: [flexcoders] Cairngorm and MVC: Quickie >Date: Mon, 21 Aug 2006 22:32:30 -0000 > >Hi all. Just wondering if I have figured this out correctly. > >In an MVC/Cairngorm application, it is ok to have as many models as I >determine based on my data needs. > >Then, I would have one ModelLocator class (which extends the core >Cairngorm one) mapping to each model and instantiating variables for them. > >Then I reference the model locator in the views to which it is relavent. > >But all apps only possess one Controller. Is that right? > >So, simply, 1 Controller/1 Model Locator/1:N Models/1:N Views -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
