No that is very smart... I do it that way as well for my projects. It is neccesary the bigger the application. Many people do this as well. So keep going! Dimitrios Gianninas RIA Developer Optimal Payments Inc.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Merritt Sent: Thursday, December 28, 2006 9:59 AM To: [EMAIL PROTECTED]; [email protected] Subject: [flexcoders] Multiple Model Locators 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 -- WARNING ------- This electronic message and its attachments may contain confidential, proprietary or legally privileged information, which is solely for the use of the intended recipient. No privilege or other rights are waived by any unintended transmission or unauthorized retransmission of this message. If you are not the intended recipient of this message, or if you have received it in error, you should immediately stop reading this message and delete it and all attachments from your system. The reading, distribution, copying or other use of this message or its attachments by unintended recipients is unauthorized and may be unlawful. If you have received this e-mail in error, please notify the sender. AVIS IMPORTANT -------------- Ce message électronique et ses pièces jointes peuvent contenir des renseignements confidentiels, exclusifs ou légalement privilégiés destinés au seul usage du destinataire visé. L'expéditeur original ne renonce à aucun privilège ou à aucun autre droit si le présent message a été transmis involontairement ou s'il est retransmis sans son autorisation. Si vous n'êtes pas le destinataire visé du présent message ou si vous l'avez reçu par erreur, veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses pièces jointes, de votre système. La lecture, la distribution, la copie ou tout autre usage du présent message ou de ses pièces jointes par des personnes autres que le destinataire visé ne sont pas autorisés et pourraient être illégaux. Si vous avez reçu ce courrier électronique par erreur, veuillez en aviser l'expéditeur.
