Flash Builder 4 and project settings flaw in its design
After having a play around with a Flex project for a few months now, I decided to uninstall the beta version that I had been using and install the final release. But I noticed that there was one thing that seemed to be lacking in the design of the workflow and settings of this application.
I have to also assume that this has been a problem with the application for a number of years, and versions prior to this release as well.
One of the things that has annoyed me with both ColdFusion Builder and Flash Builder 4, is that there are certain things that seem to be stored at the workspace level. Sometimes one has to question how they come up with these scenarios, or does Adobe not believe that workspaces can be trashed and or moved, or re-import from SVN with the loss of critical build information for that project?
After re-importing the project back into the Flash Builder 4 released version, I noticed that one thing had stopped working. It didn't take me long to work out what the problem actually is.
The project that I am working on has a custom run/debug setting where I change the URL to use a main.cfm instead of a main.html, and as the application when run setups some critical paths and stuff this can't be achieved by running a HTML file as the Application.cfc will never get run.
So once again I had to manually change this back to what it should be, and manually remove the directories that got created in the wrong locations.
I am not sure why this is not saved at the project level, where it could be passed onto other developers so that they don't need to be aware that they need to manually make this and that change.
Anyway this might be a small case scenario, but it is a gotcha that really annoys me with Adobe on both their Builder Applications.
There are no comments for this entry.
TweetBacks