Using Flex (Flash) Builder with HFCD
UPDATE: Please also check out this post (https://stopcoding.wordpress.com/2009/10/22/how-to-setup-your-projects-for-hfcd) on how to setup your projects for HFCD.
Many thanks to those who downloaded and tested HFCD in the past couple of weeks. If you are a Flex Builder user and are not satisfied with its compiler performance, you should definitely give HFCD a try. I’m going to give some tips on using HFCD here.
Uploading source files from Flex Builder to HFCD
With this latest version of HFCD, you can run Flex Builder and HFCD on two different machines. So how does Flex Builder keep the source files on the HFCD side up-to-date? It is pretty simple. First, you make sure that both Flex Builder and HFCD are running and connected. Then simply close and reopen your projects. Typically you only need to do this once. There is no need to do this every time you start Flex Builder or HFCD. After the first upload, whenever you refresh (F5), add, edit or remove any source files in your projects, the HFCD plugin should pick up the changes and upload the changed files to HFCD.
Some Flex Builder users don’t always put the files needed by the compiler in the project directories. They put those files (e.g. SWC files and/or configuration files) *outside* of the Flex Builder workspace. Eclipse/Flex Builder does not know about these files, so they will not be automatically uploaded. To address this issue, one can use the “HFCD FileSet” view in the plugin.
This “HFCD FileSet” view allows users to specify external directories. Users can then instruct the HFCD plugin to recursively search for and upload the files in these directories to HFCD.
The above description also applies to the situation where Flex Builder and HFCD run on the same machine.
Building Flex applications and libraries with HFCD
Basically you use the same menu to clean and build Flex applications.
The first clean/full build is usually slow because it’s the first and ‘warm-up’ build for HFCD. The performance of subsequent clean/full builds should gradually improve as HotSpot VM optimizations and parallel compiler builds kick in.
“Build Automatically” should be disabled when using HFCD. Why? Well, “Build Automatically” forces Flex Builder to immediately launch incremental compilations after code changes. But there is no need for that because HFCD automatically launches background incremental compilations. Other benefits? Flex Builder can’t let you save your code changes while it is building – you either save your code changes (and cancel the build) or keep the build going. With the use of HFCD, you can save your code changes continuously.