senocular.com

As Emmy Huang points out, version numbers for Flash Player 10 have changed. Basically, we're now using all of the 4 identifier values in the Flash Player version string. Before, Flash Player basically used the scheme major,0,build,0. Now, the scheme is major,minor,maintenance,build. This means that for "dot releases" of Flash Player, the minor build can be incremented to give us something like 10.1 and 10.2 etc. (Finally!) Though, granted, there are a lot more numbers to look at now. At least the new format is completely backwards compatible so it you only look at the first and third values, you'll still be able to distinguish between player versions.

Chances are by now, you've probably heard of LittleBigPlanet. If not, a week or two ago, I would have been surprised. But given that most of the people I talked to at work about it haven't heard about it, I'm starting to think it's not as well known as I had once suspected. But maybe now that's changed with the latest news regarding its release.

At the top! Yes, well, maybe you *put* them closer to the bottom, but Flash still declares them at the top of the function. Confused? Lets take a look at some examples.

This is something I had meant to post for a while now, but didn't, and after FlashCamp this past weekend, I regret having waited since I know a lot of people had problems with this...

I don't know about you (and I know a lot of people are different), but every time I create a motion tween in Flash, I have a specific workflow. That workflow is, creating a symbol, adding a keyframe in the timeline at the end point of the tween (using F6), modifying the symbol at that location, then right-clicking in the generated span and selection "Create Motion Tween". Tah-dah! a motion tween! Of course now, whenever I do that in CS4, the end result is a stagnant timeline that screams "You fail at life!"

I've slightly reworked the spinning earth (globe) example in the FlashCamp samples, dropping the custom 3D transformation function in favor of using new native APIs including Matrix3D, PerspectiveProjection, and the oh-so-important Utils3D.projectVectors. In turn, the code should be a little easier to read with less going on (the new APIs handling much of the work).

During FlashCamp over the weekend, I mentioned that for one of my examples I managed to get path data out of Fireworks with a simple script. I have now posted that script online.

There isn't any interface for using it at this stage - it just reads the points and dumps them to Fireworks' JavaScript's standard out (which usually goes nowhere). But you can easily get the desired results by running it in the command prompt panel (in Tutorials and sample files).

Just caught wind of a site that allows you to check the SWF version (among other things) of a SWF online or from your desktop using the SWFReader class. It's called http://swfversion.com/ and even allows you to specify which SWF you want to check via URL; example: http://swfversion.com/?u=http://senocular.com/flash/files/bubblegrid.swf

Ahhh... those good ole days where we dealt with the 21/31 fps Mac bug.

If you've been keeping yourself up to date with news and blogs, you probably already know this by now, but it is my obligation to make sure you know it again. Flash Player 10 is here!

Along with all the fancy new features, Flash Player 10 also sports some improved stability and boatload of bug fixes. Get your copy today.

First I want to say I had a blast at FlashCamp. Despite it lasting all weekend, there still wasn't enough time. A special thanks goes out to Dom for organizing the event as well as to all of those who participated in the hackathon contest. It truly was a chore to have to pick a winner. Congratulations to those who won, and a job well done to everyone else.

In case anyone missed it (either FlashCamp, or my presentation), I have all my "Enhanced Drawing API" files available on http://typeof.info/flashcampdapi/. This includes the presentation itself (pptx and pdf formats) as well as all of the source files for the demos.

Its no secret that Flash Player 10 now supports "3D Effects" - a new feature allowing developers manipulate display objects in a 3D coordinate space. The Flash CS4 authoring tool allows you to apply these effects to display objects on the stage and animate them over time using the timeline. If you do this, however, you may notice a dramatic jump in file size for your SWF. As soon as you make anything 3D, you've instantly added at least 13K to your published SWF. But why?