Archive for the ‘Flash Development’ Category


FlashBuilder – How to Instantly Refresh your SWC’s

SWC files are a necessary part of using Flash Builder. They allow you to access library items from an FLA or pre-packaged classes without having to load external assets, and as a bonus they show up in the auto-complete pop-up. To use them from an FLA, you’ll need to set the publish settings to Export SWC, and then in your Flash Builder project right click your project and add that SWC in your project settings.

The annoying thing about SWC’s is that when you make changes to them and re-publish your file, those changes will not necessarily show upĀ  in Flash Builder right away. Even if you right click your project and hit “refresh”, for some reason the program does not also refresh your SWC. The timing may appear random, but there is a way to force Flash Builder to grab your most recent SWC instantly.

And here’s how: simply make a new variable with a colon (ie var blah:). As soon as Flash Builder’s auto-complete options show up with a list of classes, it’ll have updated everything. There’s no need to import anything or keep the variable — creating the auto-complete pop up is all it takes.

Simple… and effective!

Adobe Web Premium CS5 Review

Let me preface this review by saying that I’m a Flash developer & designer, and I’ve been using Flash, Dreamweaver, Photoshop, and Illustrator for 10 years now. I also animate and photograph too, so I use just about everything in this package pretty thoroughly.

There are so many products in this suite that it wouldn’t make sense to talk about everything specifically, so I’ll just note some standout positives and negatives that I’ve encountered. I’m not going to comment on the differences between CS4 and CS5 because I skipped CS4 for a number of reasons, some of which were not entirely resolved in this upgrade either. Many in the industry feel like CS3 was the last “great release” by Adobe/Macromedia, so using CS3 as a benchmark works well for me. If you want an opinion on something specific just leave a comment and I’ll update the review.

Before getting into it, I would like to express a very specific concern and frustration that I have with this entire suite. Adobe is making a move to make all of its applications use a unique, proprietary Adobe interface, which although shiny and nice is neglecting a slew of standards and behaviors that people are used to on Windows or OSX. CS3 used windows and panels that were tied into the user’s operating system, so for example the scroll-bars in menus were the same ones you’d see in any other program. That means that they worked the same way, looked the same way, and felt the same way to click, roll your mouse wheel over, etc. CS4 and CS5 have moved away from this and in doing so caused a ton of headaches that you’ll soon learn about if you buy the suite.

read more

Flash 3D Transformations & File Size

Today at work we had a curious situation — a simple 40k banner was somehow using 23k of Actionscript bytes even though its only code was a number of stop()’s and some navigateToURL()’s and URLRequests. How was this possible?

Theory #1 was that tweens could have had something to do with it. Could the new tweening system actually be using AS? I created a test file including classic tweens, shape tweens, and “new” tweens. The result was 0 Actionscript bytes.

Theory #2 was that Blending Modes could be a factor. Again, 0 bytes.

Theory #3 was that 3D transformations could be the culprit. There was a simple 3D effect used at one point in the banner. To test this, I made an extremely basic AS3 file and applied a slight 3D rotation to its only MovieClip. I published and, voila, there were 23k of Actionscript bytes in the size report.

It’s odd that classic and “new” tweens hardly affect file size at all but 3D manipulations have to include a significant sized AS library. Unfortunately I don’t know what resulted in this decision by Adobe, but if anyone has some insight I’ll be sure to make an addendum to this post.

OSX Audacity LAME Library and Flash don’t get along.

The LAME Library 3.98.2 does a tricky thing when you import an encoded MP3 into Flash. It works for just about everything EXCEPT when you want to seek to a specific time. This can be off anywhere from a few milliseconds to a few seconds. It’s horribly annoying. I nearly jumped out of a window before trying to see if encoding had been the problem the whole time.

#Edit: I’ve recently discovered the reason why this happens. Apparently when you compress an mp3 using Audacity at a bitrate lower than 128 kbps the frequency is set at something unusual. Flash gets along with 44.1 hz and 22.05 hz but if you hand it something funny it responds… funny.

That is all. Avoid smashing your head into walls and use a different encoding if this happens to you.