Hello, I would like to be able to target my class library so I can re- use AS3 classes I have written. In the Flash IDE I set this in the Preferences though I am not sure where I set this when compiling using fcsh through the AS3 bundle. I am guessing it's in the flex- config.xml file or maybe the project specific project-config.xml file? Also, do I need to manually copy over classes I have used from my library into my project folder in order to share the project with other developers or is there an automated way of exporting the source files in this way?
Thanks guys, Alistair
-------------------------------------------------------------------------- Alistair Colling Interactive Developer
FPP Brand Communications (Newcastle upon Tyne) The Courtyard Dinsdale Place Sandyford Newcastle upon Tyne NE2 1BD Telephone: +44 (0)191 261 6662 Fax: +44 (0)191 233 2511
This transmission is confidential and intended solely for the person or organisation to whom it is addressed. It may contain privileged and confidential information. If you are not the intended recipient, you should not copy, distribute or take any action in reliance on it. If you have received this transmission in error, please notify the sender at the e-mail address above. FPP Design Limited. Reg. Office: The Courtyard, Dinsdale Place, Sandyford, Newcastle upon Tyne NE2 1BD. Registered Number 3775564. Registered in England and Wales. Visit our website at http://www.fpp.net/
I am guessing it's in the flex-config.xml file or maybe the project specific project-config.xml file?
Either of those options would work, with the flex-config.xml file being entirely global.
Also, do I need to manually copy over classes I have used from my library into my project folder in order to share the project with other developers or is there an automated way of exporting the source files in this way?
For sharing source I recommend that you use a versioning/source control system (ie subversion). Then check working copies of it out into a library directory on each development machine, or, preferably into each project (as the library should be developed separately this will allow you to keep the project tied to specific revision if need be).
Alternatively you could look into distributing your library to other developers as a swc.
Cheers, Simon