New media has met its match.

The following article assumes you have a solid understanding of Flash AS2 and the Flash interface and skips all basic Flash setup instructions and explanations in effort to provide you with quick, concise information.

You’ll occasionally find your client asking you for an executable version of the application you built them. Chances are they’ll also want that executable to open fullscreen. Flash can quickly compile executable files for Windows and Mac environments.

Step 1: Adding Some ActionScript
In the actions layer of your application, specify the following (place it at the top, underneath your class import statements, for consistency and best practice):

AS2:

AS3:

Detailed information about fscommand() and its additional parameters is beyond the scope of this article.

Step 2: Publish Settings (AS2 and AS3)
In the Formats tab in Flash’s publish settings (File > Publish Settings), you’ll see a bunch of options. The last two checkboxes allow you to export a .exe (Windows) or .app (Mac) version of your application.

If you just need to provide a .exe, you’re all done with the export step and you can skip to Step 4. If you’re providing a .app version instead/in addition, move on to the next tricky step…

Step 3: View Package Contents of .app File (Mac Executables Only, AS2 and AS3)
Now that you’ve published out your .app file, locate it in the publish directory you’ve specified in the Publish Settings panel. This file will launch to fit your monitor’s window, however with uncertain inconsistency and most likely with a browser title bar. No problem, here’s the fix:

• Right click on the .app file and choose Show Package Contents
• Locate the Info.plist file and open it in TextEditor or a similar editor
• Browse towards the end and locate the end of the <array></array> node
• Add the following node, alphabetically, as an additional <key> node:

<key>CSResourcesFileMapped</key>

<true/>

<key>LSPrefersCarbon</key>

<string>YES</string>
<key>CSResourcesFileMapped</key> <true/> <key>LSPrefersCarbon</key>
<string>YES</string>
<key>LSUIPresentationMode</key>
<integer>4</integer>
<key>NSAppleScriptEnabled</key>

<string>YES</string>

<key>NSHumanReadableCopyright</key>

<string>Copyright 1996-2009 Adobe Systems Incorporated and its licensors. All Rights Reserved.</string>

• Save your file
• Now test your app

Note that your XML list may differ from the example above. As long as you drop the <key>LSUIPresentationMode</key> node above in the right alphabetical order, it will yield the desired results.

Step 4: Packaging your files for delivery
Now that your executable files are ready for delivery for either platform, it’s time to package them up and get them ready for hand-off.

Create a new folder to house your .exe and/or .app files. These files act like a .swf, so don’t forget to include all external-loading files (XML, folders, images, etc.) in your delivery package. You’re all set.

If you’re a Flash developer, at some point in time you’ve had to build and optimize rich media banners for your clients.

Establishing a consistent workflow and following some simple guidelines is the key to success in banner optimization. Most of these techniques are basic and common knowledge to seasoned developers, but should be a great starting point for novice to advanced programmers.

Although not meant to be a definitive list, I’ve found the following steps work well when optimizing rich media banner units:

1. Always request specs for file size before development begins:

• Banner dimensions
• File sizes
• Frame rate
• Player version

2. Polite downloads (when available): is 30-40k initial, 70-100k additional (client specs may vary)

• Base .swf should be the 30-40k max, and the additional content should load in via a second .swf

3. If you are doing simple animation, use TweenNano instead of TweenMax when programming dynamically to save a few k

4. Recreate assets in vector whenever possible, unless it is a complex vector, then it may make sense to import the asset as a bitmap

5. Combine images whenever possible

6. Remove all complex bitmap filters from bitmaps in Photoshop, and replicate them with Flash’s filters using the Properties menu (you’ll need to convert all bitmaps to MovieClips before you can apply a Flash filter)

7. Only include the text characters you are using when embedding fonts in dynamic text fields

• Occasionally it makes sense to flatten text into bitmaps (even though this is bad practice) to get the files under spec

8. Under publish settings, do the following:

• Set the target Flash player to the version spec’d out by the client
• Change bitmap compression settings as needed (individual bitmap settings may need to be enforced as necessary)
• Check Omit trace actions (occasionally knocks off a few k)
• Check Generate size report to review asset weight in your .fla and allow you to locate and resolve problem areas contributing to file size overages

Following these guidelines should keep you out of trouble. If you’ve found any other tips that have worked well for you, please let me know and I’ll update the list. Enjoy.