RE: [flexcoders] Re: Flex Project Struture

2008-09-18 Thread Ryan Graham
: 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

RE: [flexcoders] Re: Flex Project Struture

2008-09-17 Thread Ryan Graham
If you are using Subclipse in Flex Builder, it does a pretty good job of automatically leaving out said files. Here are some for example in a standard Flex Project folder: * .settings folder * .actionScriptProperties * .flexProperties *

Re: [flexcoders] Re: Flex Project Struture

2008-09-17 Thread Howard Fore
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

Re: [flexcoders] Re: Flex Project Struture

2008-09-17 Thread Douglas Knudsen
these .files suck for distributed teams though, unless you force all your devs to use the same exact resource setup, something I'm loathed to here any manager tell me :) use svn:ignore to ignore files and not include them in your SVN repos. In Subclipse, right click the file or dir and choose

Re: [flexcoders] Re: Flex Project Struture

2008-09-17 Thread Josh McDonald
Yeah that trick's not bad, that's what we're doing for build.properties etc. I find in *most* cases there's nothing system-specific in our .actionscriptProperties (mainly defines and keep-as3-metadata, etc), so we get away with it :) What isn't any fun, is that there's *something*, *somewhere*