Our XML-based quiz document is really going places. We explained it and then loaded it into Flash in the first two installments, so logically it's time to make some sense of it using Flash's superheroic XML parsing abilities. I really can't stress enough how much better XML parsing is under ActionScript 3, because if things hadn't changed, there certainly would have been a nice padded cell waiting for me at Bellevue right about now. So join me as I share the joy of reading XML in Flash with you, the most loyal reader.

Ah, the simple, venerable trace command. Everyone who has ever written even a single line of ActionScript -- from the newbiest of designers to the most seasoned programming professional -- has doubtless become intimately familiar with this most basic, approachable, and useful command. But love turns to hate if you ever need to see what's going on when your Flash movie is playing in a browser, where seeing a simple trace can rapidly become an exercise in frustration. Fret no longer, fearless readers, as this guide aims to get everyone in on that sweet, sweet browser tracing action.

Let's face facts, folks: sometimes just scaling your entire Flash movie to an arbitrary window size won't cut it. A prime example of one of those times would be if you're using Flash to create Web-based applications, where your users would rightfully expect to have the application interface scale intelligently to the size of their browser window. Flex Builder can do this through a simple GUI panel, but the process is a little more involved if you're using Flash CS4 Professional, which is where we'll pick things up.

One might naturally assume that a series of articles about building a Flash quiz engine may actually impart some knowledge about, oh, say, Flash. With that in mind, in this installment we're going to rectify the absence of any Flash in part one by firing up Flash and writing some ActionScript 3, with the exciting goal of loading the XML document we produced last time. Without further ado, let's dive right in.

In the first installment of a multi-part series, we’re going to begin the process of creating an XML-based quiz engine using ActionScript 3 in Adobe Flash CS4. We’ll start slowly today by figuring out what features we want to include and how those features will translate to the structure of the XML template we’ll eventually use to populate the Flash playback engine. So, to kick things off, let’s ask the obvious question: what do we want this thing to do?

Believe it or not, there are still folks out there using Director for multimedia authoring, even as Adobe pushes the Flash platform ever forward and preps AIR as the technology of choice for desktop-based applications. And while it's been more than a year of silence since the "Director is not dead" proclamation was issued by Adobe's former Director Product Manager, in the interest of keeping the fires lit, here's a tidbit for how to make Director projectors (with the help of the essential Buddy API Xtra) recognize whether they're running on an Intel or a PowerPC-based Mac.

Regardless of what you may specifically think of the CS3 iteration of the venerable Dreamweaver visual Web editor, even the most hardened skeptics would probably be forced to (grudgingly) agree that the integration of Adobe's Spry framework for Ajax into Dreamweaver CS3 is, to put it very technically, pretty freaking cool.

LightWave 9 has been available for months, but it's taken the promise of the forthcoming Universal Binary release to finally get me to slip out of the cozy old slippers that were version 8.x. And despite my being behind the curve, gentle reader, I hope you won't mind me stopping by from time to time to convey some LightWave 9 knowledge, much as I did for earlier versions. So I'll stop pretending I'm writing a teaser for Masterpiece Theater here and just get to today's screencast, which just so happens to be an introduction to LightWave 9's amazing Node Editor.

If you were with me for the last installment, you're already hip to the palpable excitement in the air that has already worked its way into a fever pitch. Today we're going to--wait for it--take the content we made last time in After Effects and put it all together in Flash. I, for one, can't wait, so let's get this party started.

Only in a time of incredible blurriness between formerly separate disciplines like motion graphics and interactive design could programs such as After Effects and Flash be considered complimentary, but in this age of the proverbial blending of chocolate with peanut butter, the two aforementioned Adobe stalwarts have enormous crossover potential. And while citizens of the world (or, at least, users of Flash and After Effects) wait for both programs to emerge from the midst of their respective product cycles, we're going to examine a few ways that you can apply skills and techniques acquired in one program to the other.