there any opinions on the use of multiple modelLocators in a (potentially)
very large Flex2 app.
Consider, for example, a Main.mxml that uses a tabNavigator to view five
separate custom components, each of which is a large 'sub' application.
These components are being developed by a team of developers located in
different continents, thus it is necessary to establish a structure that
permits 'sandbox' code development, while ensuring that each component fits
nicely into the 'big picture'.
Are there negative implications in creating a modelLocator created for each
component?
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure. If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---------------------------------------------------------------------------
--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
SPONSORED LINKS
| Web site design development | Computer software development | Software design and development |
| Macromedia flex | Software development best practice |
YAHOO! GROUPS LINKS
- Visit your group "flexcoders" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
