One of the alternatives I have experimented with is linking a project to the source of a library, which basically copies the library source into a specific project. There seems to be an issue with this implementation as well: while Adobe's documentation says that when the source location's files are updated all linked projects' components will be updated, this does not seem to be the case. In fact, it seems to simply copy the library's contents once to a directory beneath the linked project, and any changes done to the linked directory are not properly updated.
The current workaround is to copy the library's source into a project's directory structure, and copying again when the newest version of the library is needed.
This is not the greatest solution, as it is difficult to couple with source control and doesn't allow the custom component icons to display.
Does anyone know a better solution for a library in Flex 2?
Thank you all.
__._,_.___
--
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.
__,_._,___
