That sounds like a good path to follow -- especially if you set up automated ANT builds for your flex library project, perhaps once or twice a day. That way, any apps consuming the library will always be referencing a current build. This could result in runtime errors for older projects though if you begin changing the interfaces for the components contained in the library. At that point you could try checking out the flex library project from the SVN, building, and then linking the flex library project to your main flex project. This should allow you to have a snapshot of the library that you know will work with the flex project at that point in time. HTH, Ryan
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Howard Fore Sent: Wednesday, September 17, 2008 1:05 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Re: Flex Project Struture Have you tried making a linked folder in the src directory? File > New > Folder > Advanced > Link to Folder in file system. This creates an alias in your project to that folder. Haven't tried it myself, not sure how the compiler is going to like it. The other option would be to put the alias in the operating system, using junctions in Windows or aliases/symlinks in OS X/Linux. I would expect the compiler to have no issues with those as the operating system should make them appear as real directories to the program. On Wed, Sep 17, 2008 at 3:51 PM, flexaustin <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: What about sharing components. For instance, we have a project just completed with several as components. We want to use some of those same AS components, but don't want to copy them to our new projects directory since when changes are made in the AS components for the old project we need them to show up in our new project. So we want to point to the same library or folder for both applications. -- Howard Fore, [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> "The universe tends toward maximum irony. Don't push it." - Jeff Atwood This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
