StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>There's no need to use <code>mxmlc</code> on the command line just to be able to add compiler flags. Right click your project in the Flex Navigator, select Properties and then Flex Compiler in the dialog that appears. There you can add any extra compiler flags. </p> <p>Not sure that there's very much to do though, more code means more compile time, that's just the way it is. If you're not doing a release build (or whatever it's called in Flex Builder) it's unlikely that your compiler settings include <code>optimize</code> to begin with. Better choices to try would be <code>-incremental</code> (which only recompiles the parts that have changed) and <code>-keep-generated-actionscript</code> (which stops the compiler from deleting the ActionScript files it has generated from your application's MXML files).</p> <p>I very much prefer using <code>mxmlc</code> on the command line (by way of Ant) compared to Flex Builder. Although I don't think that the latter compiles any slower, it feels more sluggish in every way. Using Ant also makes it possible to do more than just compilation when building, and conditional compilation (only compile a SWF or SWC if the source code has actually changed). Check out <a href="http://blog.iconara.net/2008/02/22/quick-tips-to-speed-up-your-ant-build/" rel="noreferrer">a blog post of mine</a> for more info on that.</p> <p>What you could try is the <a href="http://labs.adobe.com/wiki/index.php/Flex_Compiler_Shell" rel="noreferrer">Flex Compiler Shell</a>, another command line tool that can speed things up. Basically it tries to keep as much as possible in memory between builds, so no need to wait for things like the JVM starting up (the Flex compiler is a Java application). On the other hand this is sort of what Flex Builder does anyway.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload