these are the environment variables flash understands where <x> is your flash num or C and <lang> is your install language
$(AppConfig): Common/Configuration folder in the Flash install directory (/Applications/Adobe Flash C<version>/Common/Configuration)
$(LocAppConfig): en_US/Configuration folder in the Flash install directory in English (respective folders for other languages) (/Applications/Adobe Flash C<version>/<lang>/Configuration)
$(UserConfig): Configuration folder in the current user's Local Settings directory (/Users/<user>/Library/Application Support/Adobe/Flash C<version>/<lang>/Configuration)
$(LocalData): same as UserConfig
$(FlexSDK): set by the user in preferences. May use other variables, and by default uses $(AppConfig)
Hi, Yeh, I'm aware of the variables, however I would like to use a custom one, is there anyway of defining these? Or using a OS Enviroment Variable as I had described before, I'm sure this can be done or if not should be added to flash.
If anyone can confirm this would be brilliant.
Thanks if thats the best we can do for now thats great. I would really love to see some functionality like this added to the flash IDE though, It's sort of present in Flash Builder and would make assets files a lot more portable I think.
Thanks for the info though
You can use relative class paths as well. I find this pretty portable.
You're welcome and good luck!
To be honest, if you really want the better solution you should use a code repository. That lets each person place code in the same folder as the project which will be found by Flash without adding in any paths at all. It also lets the user use a global variable to their own preferred folder. The added protection of version management and collaboration can't be beat either.
You should consider setting something up on github or installing subversion on a server for everyone. I'd be lost without it.
1 person found this helpful
sinious the problem with doing that is that the changed path gets into the code repository as well, so you wind up with everyone going back and forth changing it to their own value, which is a hassle. If you use relative paths and a standard project setup, then it all "just works" without a problem.
For example, this is the setup I use:
.bin <swfs are output here
We have a "base project" that you check out to start a new project (we do heaps of similar work), and the paths are already set up to be relative. Having each project point to its own copy of the core code allows for fine-grained control of which revision you're using--we've even pointed deliberately to old versions or branches on rare occasions.
The bin folder is actually shared with the website repository, which is in a different directory from the Flash source code (in the website, it has a different name). This allows the generated swfs to be easily updated and ensures that the latest XML is being used both for development and on the site.
The "thisProject" folder actually includes a Flash Builder workspace with all the standard shortcuts, etc., already set up. This is primarily because of how the "default path" works when you create a new Flash Pro project in FB. Because we output a level up from the workspace, we hack the .metadata folder every time, but that's a small change.
Good luck with getting atomic freelancers to adopt your directory philosophy Amy.
Well I understand about using relative paths etc and we do already use git for sharing the project files.
But we would still very much like to use variables to point to paths.
Some developers are messier than others and don't honour folder structures also some not technically savy artists I think would benefit from this feature.
It just would have been very nice to use system environment variables or be able to set up custom variables within flash for this.
I will just switch to using relative paths and continue trying to keep these developers and artists in order.
Thanks for help everyone
Freelancers=people you're paying, correct?
We actually have people on salary that had a hard time understanding why things just worked better when they did them the way I recommended. However, after finding that doing things a different way is really frustrating and doing them the way I suggest isn't, somehow the issue resolved.
I would think this would be even easier in a situation where you can tell them that you're not going to pay them for work that's not submitted in the correct format or for hours they waste due to not setting things up as requested.
I wish. Some of the companies I work with have excessively short project timelines. My company often operates atomically as add-when-needed bandwidth to hit these crazy schedules.
I often find myself in a soup of my clients available resources, my companies resources and some random number of other freelancers and companies. I've never had a client enforce something like that. I think they know the nature of flash/air projects. Short lifespan.
Application projects like C#? Yes, definitely a structure.