I can't see any problems with that. Another way is to let your one and only ModelLocator reference your models. It looks like you are trying to make the ModelLocators a model, which is ok in small projects, but in bigger ones, it is more a locator than a model.
Cheers, Ralf. On 12/28/06, Kevin Merritt <[EMAIL PROTECTED]> wrote:
I am migrating a fairly complex RIA from Flash to Flex and am trying to redesign the entire framework using Cairngorm. I have read numerous examples and tutorials explaining the Model Locator, and am sold on the idea of using "business logic to manage views (per Alex's blog) however, I am wondering if there are certain cases where it would make sense to use multiple Model Locators and segregate them based on the types of data they are locating them. For example, I have grouped some of my data objects in the following way: Application Data - objects which allow me to customize the interface and user experience for different clients. User Data - objects with hold information about the user, including preferences & access levels Group Data - objects which hold user defined groups that hold contacts & schedules Contact Data - objects which hold lists of contacts and their specific infor such as addresses, emails, phones Sched Data - objects which hold info about event schedules for each contact what I am wondering is if in this case, it would make things more manageable if I set up a couple different Model Locators such as: AppModelLocator - to access Application Data UserModelLocator - to access User Data GroupsModelLocator - to access Group, Contact & Sched data Is this a smart way to approach this OR am I creating potential problems for myself by doing it this way. What am I missing? Is there anything on the web that talks abotu multiple Model Locators in a single app. Thanks for the help! - Kevin
-- Ralf Bokelberg <[EMAIL PROTECTED]> Flex & Flash Consultant based in Cologne/Germany
