Flash Catalyst / Flash Builder Workflow Optimizer
Workflow Optimizer is a small and lightweight tool which helps Flash Designers and Flash Developers to work around some of the temporary limitations with Flash Catalyst.
The application allows you to automatically extract the contents of FXP / FXPL files and put them into a configurable directory and can hence replace some of the tedious export / import actions from Flash Catalyst to Flash Builder.
The application is written in Flash Builder 4 with Flex 4 and AIR, it uses the as3preferenceslib for persisting the directory and file information and it uses Mate Flex Framework as the application controller.
Next step is to add support for running as a service by adding some Merapi classes and examine even better ways to help optimize the FC / FB workflow.
You can download and install the latest version from the Adobe AIR Marketplace here…
http://www.adobe.com/cfusion/marketplace/index.cfm?event=marketplace.offering&offeringid=13424
Sources are available at Google Code…
http://code.google.com/p/workflowoptimizer/
You can download the binary from here…
http://petermolgaard.com/projects/workflowoptimizer/WorkflowOptimizer.air.zip
Sources will soon follow…
hello and thanks for sharing. I’m on mac osx and I’ve just tried to use your app. I choose my catalyst project, set the path to a new created flash builder project and update. After the update flash builder comes up with an error window that reads see below. I’m doing something wrong of what else?. In any case Thanks.
“Multiple problems have occurred”.
1 – refreshing project:
An internal error occurred during: “Refreshing project ‘Argeo’”.
Error reading persistence file L/Argeo/.flexProperties
2- refreshing workspace:
Problems occurred while refreshing local changes
Problems occurred while refreshing local changes
Errors occurred while refreshing resources with the local file system.
Failed to read the project description file (.project) for ‘Argeo’. The file has been changed on disk, and it now contains invalid information. The project will not function properly until the description file is restored to a valid state.
… and needless to say the project is not readable anymore.
Hi Jadd,
Unfortunately it seems there is a problem with the file parser when it comes to handle the meta files such as the actionScriptProperties, flexProperties and project files.
If you ensure to check off the MXML only, then it will only handle MXML files which essentially is what we want.
I will update the app a.s.a.p.
In the meantime, fixing your project should be straightforward. Close the project, open the 3 project files in a text editor and remove all of the MXML code which has found its way into them and the save them again.
I apologize for the inconvenience.
// Peter
I have updated the application to prevent a similar thing to happen again.
The version is now 0.1.2 and it enforces to only take MXML files which are not affected by the bug.
I have removed the ZIP file download, instead you can now download it from the Adobe AIR Marketplace…
[...] Molgaard came up with a Flash Catalyst / Flash Builder Workflow Optimizer Air application. It’s a very early thing so I won’t complain, at least he [...]
Hi Peter,
Back in the days your application got me thinking, so I’ve pushed the concept a little bit further:
http://www.flexstuff.co.uk/applications/catalystbuildersync/
I thought you might be interested.
Gilles
Hi Gilles,
Your application looks really cool, its great to have been part of spawning it.
I’m looking forward to giving it a whirl on my Flash Catalyst over the weekend…
// Peter