That’s a while I tell myself I should have a closer look at all the Flash Publish Settings available when opening the Publish “Settings…” dialog bog in CS3. So I’ll check that now – starting with the “Flash” tab
1. To start with, It is possible to save a profile for the Publish Settings. I never really used that…
2. Version: the Flash Player version the animation should be able to run in.
3. Load order: specify in which order (bottom up or top up) the layers of your flash animation get drawn on the scene over the slow connection. I don’t believe I ever saw an animation where I had time to see the layers rendering at different time (I actually though they would all be loaded before rendering?)
4. ActionScript version: If you set ActionScript 3, there are other intesting settings from the “Settings…” button:
4.1. Errors: “Strict mode” won’t let the animation compile if their are warnings. “Warning Mode” display additional warnings. (which won’t prevent compilation)
4.2. Automatically declare stage instance: When you associate a Flash file with a document class, ticking this will save you from having to declare all stage instances as class variable. On the other hand, declaring your class variables may make it easier later on to quickly assess the content of an animation from its class file, plus it gives you access to code hinting (e.g. from Flash Develop). I keep this unticked.
4.3. Optimizer: One wonder why one should not tick this. Maybe it slows done compilation time? Does not seems so though.
4.4. Dialect: ActionScript or ECMAScript. ECMAScript is a vendor-neutral language specification for client-side scripting (like JavaScript) , as far as I can remember.
5. Generate Size Report: Quite handy, generate (in the output window as well as in a txt file) the breakdown of the size of a Swf (with the size of each image/font/media… embedded in the flash animation)
6. Protect from import: Seems to be to protect your swf file to be reversed-engineered to a FLA (you need then to give a password). I am not sure against which reverse-engineering tool this does work though.
7. Omit trace action: as said, prevent the trace to be printed. Some seems to see this feature as a reason not to clean the trace() call all over their code.
8. Permit debugging: ticking this, you can debug your flash animation with the stand-alone version of the Debug Flash Player (available in Flash install directory/Players/Debug/). However it seems to be able to debug only swf file located in the machine where it is running (never tried that yet).
9. Compress movie: self-explanatory
10. Export hidden layers: As it says, if unticked, will not export the hidden layers of your flash animation. Took me a long time to find it out when movieClips were suddenly disappearing from my animation, after a developer unticked this by mistake. I am not sure I really see the point of this setting, as we can set unwanted layers as guides to not publish them anyway.
11. Export SWC: Export components, which seems to be reusable. I’ll need to dig further in this one.
12. Script time limit: I guess this is the time a script is allowed to run before poping up a message that “a script seems to slow down the navigator”
The following seems to be compression settings, that I never had to change so far.