Flex Builder Project Setup in a CFEclipse and Subversion Environment
I am first and foremost, a ColdFusion developer. And I’m a little idiocyncratic as to how I organize my projects in directories and files. My “project root” is not web-accessible, but usually contains ALL the project assets, including CFCs, CFMs, etc.
I got really annoyed that Flex Builder put everything in my workspace when creating a new Flex Project. It was not immediately intuitive how to move the main application .mxml source file outside of the workspace. And I wasn’t about to point my project path to my webroot because it would put all the Eclipse and Flex Builder property files there (which would clutter up the Subversion repository for the project).
So after about two days of futzing and conferring with more experienced Flex developers, I figured out exactly how to tweak all the poorly-documented settings in the Flex project Properties to accommodate me. Now I keep the Flex project in my workspace, but all the source files and compiled swfs end up in my webroot’s project directory, and thusly in Subversion via a single click.
I mostly documented this for myself for future reference, but hope you find it helpful. The screencast is about 13 minutes long (made with Camtasia Studio) and is a 14MB file.
Cool stuff, thank you!
I was able to get rid of the compiler warning by editing the .actionScriptProperties file in the workspace directory. It had two lines, like this:
<applications>
<application path="Main.mxml"/>
<application path="src/Main.mxml"/>
</applications>
where ‘main.mxml’ was my main application. Based on directories you use, even linked ones, I would expect that the values above could be radically different.
I just deleted the second, restarted eclipse and the warning went away.
Comment by Jeffry houser — April 20, 2007 @ 12:00 am
Sweet, nice find, Jeff. How did you figure that out?
Comment by Nat Papovich — April 20, 2007 @ 12:00 am
I’ve played around with the property files before when trying to remove a Flex Nature from a project, so this was just a bit of trial and error and a bit lucky guess.
I’m working on an article about Flex Components right now, and in my current project have a bunch of different Flex applications.
When I renamed my main.mxml to "sample1.mxml" the warning came back. When I made "sample3.mxml" the default application (by right clicking and choosing "set as default application.") the error went away again.
This needs more testing, but I suspect "set as default application" and "restart workspace" will make the warning go away without editing the property files.
Or I could be wrong.
Comment by Jeffry houser — April 20, 2007 @ 12:00 am