You're stuck with having a single ServiceLocator because of how it is located, but you can have seperate ModelLocators and FrontControllers for each module.
The FrontControllers all use the singleton CairngormEventDispathcer so your event types have to be globally unique even though you are registering them via different FrontControllers. I implemented Cairngorm this way when I had a composite app and have been happy with the results. --- In flexcoders@yahoogroups.com, "Tim Ashworth" <[EMAIL PROTECTED]> wrote: > > Hi All, > > I've just started playing with Cairngorm (and have been kicking myself for > not doing it earlier) and I'm very impressed with the approach and > framework. One v v quick question though. I'm using it for an app that has > a number of modules that could be treated as standalone modules. They > interact, but basically they are their own little thing (e.g. A contact > management module, a job planning module). Using Cairngorm is it correct > (and I know there is not right or wrong) to create each of these as widgets > using the framework and sticking with the MVC style and then write code over > the top to stitch it all together or is it better to look at the entire app > as a whole and create it that way, I.e. have a ServiceLocator that holds ALL > of the data connections, a Model for the entire app? The second way feels > wrong, but I can't find anything about doing it in the modular way without > writing code over the top (which I am more than happy to do - just my > experience of writing loads of code and then finding Cairngorm is making me > pause to see if there is something I'm missing). > > Anyway - cheers in advance and Merry New Year! > > tim >
