Mims

Prepare to be devastated, ladies and gay gentlemen, for I am getting married next Saturday the 19th! As the day has been drawing closer, I’ve been more and more consumed by wedding planning as well as general stress and excitement which is my main excuse for dropping of the face of the blog.

After the wedding, I’ll we’ll be making my our way through Europe, driving from Barcelona to Amsterdam via Provence, the Black Forest, and a few Belgian breweries. I know many of you hail from Europe so give a shout out if you know some great, strange places to visit along the way!

In between tasting cake and buying championship quantities of wine for the wedding, I’ve managed to keep busy with some really great gigs. I recently built the media-rich Toyota Tundra Experience site in collaboration with Bad Assembly and Saatchi & Saatchi LA which launched this summer. I contributed Gumbo skillz to the insanely extravagant Cannes Multi-Touch Wall with Schematic. I’m also very excited for a project I recently finished in collaboration with the very talented and funny Duncan Brothers and Atom (It’s not launched yet but I’ll announce it when it is).

Sadly, I’ll be missing Adobe MAX and the infamous Flashapaloozastock even though they’re in my own back yard! But after returning in mid-October, I’m looking forward to getting back out there and working my face off! That includes dabbling in some new technology like XNA or iPhone, blogging about some of the stuff I’ve learned on my last few gigs and hopefully, getting my shit together and finally speaking at some conferences. I’m also working on a completely revised version 2.0 of KitchenSync, my incredibly underused tweening and sequencing library.

I hope you’ve all had a great summer!

Roger

Gentlemen, WE CAN REBUILD IT. We have the technology. We have the capability to make the world’s finest programming book. The ActionScript 3.0 Bible Second Edition will be that book. We can make it better than it was before. Better. Stronger. Faster.

That’s right, I’m hard at work tearing the AS3B to pieces and building the second edition from the ground up, and I can’t wait to share it with you. I’ll post more about it when it’s ready to go to press. You won’t believe all the awesome new features in this book!

While writing, I’ve been traveling the world with my trusty laptop. This summer I’ve trekked out from my home in Brooklyn to Peru, Los Angeles, Santa Barbara, San Francisco, Montauk, Pittsburgh, Orlando, DC, Los Angeles again, Seattle, Portland, and Puerto Rico. Don’t worry, I’m taking lots of photos. I love traveling!

I’ve been working on some really cool projects, too! I made a website for the most wacky, creative filmmaker of our time. I helped to design (and hopefully I will soon program) an iPhone app for a gorgeously illustrated series of books for teens. Sorry I can’t be more specific!

When I’m not doing all this I’m rollerskating, going on long long bicycle rides, watching lots of movies, exploring all the amazing restaurants in NYC, and having adventures. I’m taking an intensive culinary class at the French Culinary Institute this Fall. I also got my motorcycle license and I can’t wait to use it more! Sadly, I’ve completely fallen off learning piano, but I really hope to start again soon!

What have you been up to, readers? Did you have a great summer?

Caleb

Caleb has left New York City. He is now studying hard at Cornell University in Ithica, NY. Aside from the mathy homework, he is kept up at night trying to determine what has gone wrong with his ray tracer. However, there may not be any better reason for a nerd to lose sleep!

Runtime Environment

SWF Files
Swf files are compressed, multipurpose packages designed to contain the following data: raster and vector graphics, video, audio, text, fonts, animation, and actionscript code. Swfs can be loaded at runtime whenever necessary and can use both static and dynamic linking based upon the compiler settings. The runtime environment uses security sandboxes for loaded swf files. The security settings primarily limit the extent of filesystem access and cross-domain access that swf files can use. Adobe has provided the swf file format spec and has recently provided the FLV video format spec and has declared that they will provide the RTMP spec as well.

Flash Player & AVM2
The Flash Player runtime is a very light-weight, virtual machine and handles system calls. The Flash Player includes both AVM1 (AS1, AS2, for Flash versions 1-8) and AVM2 (AS3 for Flash 9,10+) which processes compiled Adobe Bytecode (ABC). The term AVM stands for “ActionScript Virtual Machine”*. The Flash Player uses a Deferred Reference Counting (DRC) mechanism combined with a conservative mark/sweep garbage collector. The Adobe VM uses both JIT compiling and code interpretation and may benefit from compile-time bytecode optimizations based upon compiler input parameters. AS3 computational performance is generally closer to Java than Javascript [source]. The player also maintains a variable framerate that reflects the time consumed for each frame update [source]. Each frame update consists of multiple stages that include internal player processing, rendering, and author script processing. The program framerate is the principle metric reflecting application performance.

Development Environment

Actionscript API
The Actionscript API is divided up amongst the Adobe AIR environment, the Flex environment, and the Flash environment and the Flash Player. The source for all the packages are divided up amongst swc files. Swc files are pre-compiled catalogs of classes and assets. They are similar to swf files but they are used for compile-time dependency resolution. Furthermore, the native swc’s predominantly contain code and not visual assets. An overview of the Actionscript packages is kept up to date in the Adobe Live Docs.

The Flash IDE
The Flash IDE was designed for designers, artists and animators. So, it is equiped with a layer system which reflects the stage display list and a hierarchical timeline which reflects the temporal nature of the runtime. The objects placed on the stage are represented by the timeline and can be “tweened” (using runtime interpolated 2D geometric transformations or custom shape morphs). The same timeline is also used for object creation and destruction. All stage instances are confined to a small set of native data types including: MovieClips, Sprites, Shapes, TextFields, Videos, and Bitmaps. The IDE also has a library that contains source objects for all stage instances and even instances that aren’t used on the stage. Flash projects often have several build targets (compiled swf files) that use parts of the project codebase. After Macromedia was purchased by Adobe, the Flash authoring environment has been updated to provide much better interoperability with the Adobe Creative Suite.

Adobe Flex Builder
Flex Builder is an Eclipse-based Actionscript IDE for writing and compiling swf files. Flex Builder is primarily designed to build “Flex” projects which can be written in an interface tagging language known as MXML. MXML is a declarative XML langauge used to define interface elements in a project. MXML files provide the “view” in the MVC software design pattern. Flex Builder also provides plenty of useful features like code completion, syntax formatting, active debugging, memory profiling, and project building that expose errors and warnings during development time. Because the Flex framework is not bundled with the Flash Player, Flex projects must statically link to all swc assets specific to Flex which amounts to greater than 500kb. This is very unnatractive for most users, thus Adobe has provided means by which the download can be significantly decreased. Flex Builder is also used to deploy applications for the Adobe AIR platform. Adobe AIR is a desktop runtime that combines webkit with the AVM2 portion of the Flash Player. AIR can be likened to a closed source Java SE runtime but provides a smaller learning curve and greater accessibility than what comes with the Java ecosystem.

Compiler
Since Adobe has launched the Flex platform they have provided free access to their Flex and Actionscript compiler and SDK. They have also provided open source projects under the Mozilla public license. The compiler (mxmlc) provides an impressive amount of flexibility and customization for swf compiling. It can be configured with command line options or a configuration XML file.

* correction 09-12-2009, I had previously stated that the term AVM meant “Adobe Virtual Machine”, this is a mixup. It actually means “ActionScript Virtual Machine”. Thanks dbam.

I may be in the (rare?) position of being highly interested in two disparate technologies. The first being an online scripting language standard governed by ECMA (used in Javascript & Actionscript). The second, an open standard for real-time rendering governed by the Khronos Group (OpenGL). In recent days these two languages have faced most unfortunate developments. First the ECMA script 4…

On Nov 7, 2006 Adobe announced the contribution of their ECMA scripting engine to the open source community under the name “Tamarin”. Tamarin is also being used as the JS scripting engine for Mozilla Firefox under the name “SpiderMonkey“. It seemed like a good idea at the time of release. But now look at the situation: we have AVM2, directly connected to Firefox AND the ECMA committee –slowing the progress of Actionscript and the Flash Player (and the internet for that matter). Needless to say, this is a disappointment. But it doesn’t end there…

Though having plenty of contributors, the realm of real-time rendering is primarily controlled by Microsoft, Nvida, ATI/AMD, Apple, and (more recently) Intel. Microsoft hasn’t really contributed to the Khronos Group because long ago they decided to pursue their own 3D graphics rendering API known as Direct3D. The evolution of OpenGL has become painfully slow while DirectX and Direct3D are becoming the (de-facto) standard. Finally, the Khronos group promised to improve the long lost API by introducing an object-oriented structure in stark contrast to its current state machine model. That was in October 2007. Last week the specification was finally unveiled and it remains largely the same. Not only is this a big let down, but it will definitely damage all future 3D software and game development releases for non-Windows platforms (including future consoles). Very unfortunate.

DISCLAIMER: Both of these developments are FAR more complex than what this post outlines -and there’s justification behind both developments. But on the whole, they both seem bad for everybody (or just me?).