Blog

Some arrays can have large amounts of data at each index, making it diffucult to read sometimes for debugging purposes, ecspecially in the output window. A nice way for the output window is:
<pre><code>
trace(my_array.join(newline));</code></pre>

Or for HTML content in a text field (say a custom debugger you made in Flash):
<pre><code>
trace(my_array.join(“&lt;br /&gt;”));</code></pre>

These will display each piece of data on a newline so you don’t have to scroll horizontally and visually mark the next index by spotting the comma’s mixed in (which are the default).

… you can’t remember the last time you tweened anything.

Your told you can’t use components on a project, and you suddenly have no idea how to do the project.

Designers call you a programmer and programmers call you scripter.

You spend more time working on a Flash project in another program other than Flash (using an external code editor).

Clients have no idea that Flash can do what you can make it do.

Your implementing interfaces in Flash, not creating them.

You’ve answered the loadMovie-can’t-move-a-jpeg question more times than is humanly possible.

You can’t make a web app all in Flash because then your department doesn’t get dual developement, so your forced to use JavaScript calls to help keep state, therefore bringing up the question why did you use Flash in the first place when the initial reason was to prevent the multitude of technologies and keeping application state?

I’m currently investigating how long it will take to implement a design given to my department by the design group. I’m timing how long it takes to implement a certain component based on the design they gave.

I have a window component I made and am comfortable with. I should have a good judge of how much time and effort is involved based on how long and how hard it was to implement the interface as a whole based on just doing a small part, the windows (think Flash panels).

However, the design consists of a multi-layer Flash document utilizing many complex shapes, masks, etc. Since Flash does not have intelligent flattening abilities like Photoshop, it is very diffucult for me to keep the integrity of the design. Additionally, since it’s not my design in the first place, there may be details lost that I don’t even notice. So, I’ve decided to save time, effort, and processor by exporting them out as bitmaps. Since export image as PNG(usually) gives you an accurate representation of what your viewing in Flash (super-ceded by Print Screen), I immediately pull it into Fireworks to crop it up into the necessary window pieces. However, it has excessive amounts of transparency.

A trick I used to use in my Director days still seems to work. Basically, copy the shape. Then, do a new document. Then paste. Fireworks will trim the extra transparency (assuming there are no rogue shapes in it). Copy the image again, and do a new document, and then paste. Fireworks should have made the document the same size as the image, and the extra transparecy is trimmed. You’ll now have a more efficient bitmap for use in Flash.