★ bcdef.org ★

Only a quick note – I’ve pushed a few new iterations of Flappr to the site and the latest version is 1.04. There are a number of small fixes and subtle feature additions – you can read all about the changes or jump straight in.

That’s the lot! Development of Flappr for 2005 is finished. Still work to do next year, but for now I’ve got a sleigh to catch. Have a happy Happy everyone.

Many people on the 'net associate Flash with gratuity and obnoxiousness. Given that it's one of the more powerful tools to use for the web experience, this is both understandable and unfortunate. Often its defense comes in the form of practical examples that genuinely improve both the experience and the intuitiveness of a web site, beyond what could be done without. While this is certainly important to the broader acceptance of Flash, what I often feel are the proudest accomplishments of the Flash community are usually those farthest from the commercial sector.

For years, Flash was one of the only moderately intuitive vehicles for creating mathematical / algorithmic art. The rapid spread of the Flash Player inclined creators to work with the young Flash Actionscript format since it was relatively easy to share their creations online. The work of many such math artists was compiled into a cult favorite math art manual, Flash Math Creativity. The publisher, Friend of Ed, has a minisite where you can play with some examples from the book.

One author, Jared Tarbell, whose broader work with Flash and Processing can be found at levitated.net and complexification.net, made an experiment called "Invaders" which populated the screen with a repeating set of pixely symmetrical monsters. You can read more about it's inspiration from Jared's site. There you can also find the .FLA source if you're curious of how he's done it.

Unfortunately, that source is a few years old, in AS1 syntax, and around this time I had decided it was finally time to experiment with Macromedia's Flex Builder 2 Alpha. The reason I hadn't explored Builder earlier was because I really hadn't any purposeful place to start. Enter the Invaders.

Now I should hand out a disclaimer. You could say that the Invaders experiment is an absurd Flash piece to recode into AS3; it runs quite smoothly already, doesn't gain significantly from object-orientation, and certainly doesn't require any of the new libraries. And with that you'd be pretty spot on.

But regardless, I thought it was a reasonably short piece to translate and try my hands at the Flex Builder. So here you have it, running below in variations of AS1, AS2, and AS3 (you'll need the Flash Player 8.5 beta to see the third one). The only item I didn't implement into the AS3 version is the ability to click an invader and spawn smaller ones inside. But otherwise these should run identically (though they naturally may not look identical in the end).

Original SWF from levitated.net:

Updated to AS2:

Updated to AS3 (requres Flash Player 8.5 or higher to view):

You'll notice in the AS3 version that anti-aliasing isn't as smooth as in the previous two. I'm using the drawing API in the AS3 version rather than attaching a movie clip of a black box. The rougher edges may be due to the default quality setting (I'm not sure how to change it yet in the publish options).

Overall, I found the conversion to AS3 to be relatively less tedious than I expected. The debugger could use better integration (half the time my browser couldn't locate it). But overall, it went smoothly. Most of the challenge lay in familiarizing myself with the Builder's publish settings. I have to admit that the most welcome change I have seen in coding for AS3 is the new addChild() and addChildAt() functions, which remove a lot of the troublemaking and variable passing that instance names and depths can add to a project (and certainly did to this one). In the end the code looks a lot cleaner in AS3, and another step more conducive to extending.

I have to wonder, however, at what point I should begin committing myself further to AS3. It's exciting to experiment with a future toolset this early, but since it will require another Flash Player download, we'll have to wait a few months before clients are ready to give the green light for an AS3 project. If the early release of the Builder Alpha leads you to doubt whether learning Flash 8 is worth it's investment, there's a good discsussion brewing over at joshbuhler.com

And, in case anyone's interested in exploring this further, here's the source for all three versions.

Note: I had previously stated that the official launch of Flex Builder would not be for another year. I'd heard this somewhere along the vine, but couldn't retrace my information. And I've since received comment that the official projected release date from Adobe is much more optimistic than this, and that we should see an updated Alpha at the labs page in January. Good news! Maybe I'll fit in some more AS3 time after all...

Whether you shun or embrace Macromedia’s V2 component architecture, you’ve undoubtedly hit some headaches trying to tame them. I’ve always felt it was remarkable how complicated it was to reskin them, for example. Other parties, both for profit and not-for-profit, have been offering alternatives for at least five years now, but there’s not really any standout leader. I stand behind Patrick Mineault’s observations on the matter from two months ago.

One of the better alternatives for its emphasis on a lightweight replacement that mimics the V2 API (at a hefty $399 price tag) is the mCom set from Grant Skinner and Metaliq. You would think you’d get decent documentation and support for such a price, but both are abysmal. And after wrestling with the smallest of details, I began to wonder if the true problem was the fact that mCom was attempting to be interchangeable with the built-in V2 components. Its potential is mainly limited by the same weaknesses that hamper what already comes OOTB from Macromedia. Ever try to export classes on another frame besides 1 (so that your preloader actually works) in the same project that you reskin components? Well mCom blows up just as gloriously as V2 does. In fact, I’d say that since mCom requires relies upon the Flash IDE and attachMovie() to instantiate from Actionscript, it’s sadly just a glorified patch-up to a foundation that needs to be rebuilt.

It’s really not fair to be so critical, building components is not easy territory. I’ve been checking in once in a while to see what the OSFlash community has put together. We’ve been hearing about ActionStep for a while; it’s been in development since April. Much of its approach is beyond my expertise, but in summary, it’s an ActionScript 2.0 implementation of the OpenStep AppKit, using a Responder architecture.

From the frontpage:

There are many component frameworks that have been written over the years, but the framework that I am most fond of is the NextStep/OpenStep/GNUStep/Cocoa “Application Kit”. Because the AppKit has been implemented many times and is well documented (in books, online, etc) there is a strong base of code and designs to work from.

This is exciting because it has the potential to be just the foundational component replacement the Flash community needs.

A few days ago, the team developing ActionStep released an “Alpha 1″ release. I took a gander, and it’s still a little early to get a solid grasp of the project; documentation is pretty sparse yet. Some elements are more polished than others, and if you haven’t yet explored MTASC you’ll have a second learning curve to juggle, but the exploration piqued my curiosity. They’ve certainly completed a number of key milestones already.

You can read more about it, or snatch the alpha, right off the front page. A beta release is scheduled for January 31st, and the 1.0 is slated for (should we take a hint?) February 31st.

Note: Another component set from David Karam is also looking pretty sharp. It’s looking for help to finish off development. *nudge nudge*

If you’re an acolyte of the community-based web experience, you’ve probably used or at least heard of del.icio.us, the site that popularized tag-based social bookmarking. You’re probably also aware that while its popularity rages among web afficianados, and it would seem to benefit all humanity, it never really caught on among the masses. I suppose it was too easy to be snickered away from the water cooler for mentioning “yeah, delicious. no, it’s cool.. just put a dot between the ‘l’ and the ‘i’ and…”

Well Yahoo’s officially picked up the del.icio.us experiment, ostensibly with plans to let the originators continue where they were going. Sounds well enough. Maybe they’ll be integrated into the My Web 2.0 project. I hope that however it turns out, they can adapt the spirit of del.icio.us into something reborn into an easier-to-approach and easier-to-explore system.

Quote of note :

Yahoo officials didn’t disclose how much it paid for Delicious because it wasn’t expensive enough to have a significant impact on its finances.

Isn’t that the way? Some of the web’s best ideas are also the humblest and least money-making of ideas. Does being wrapped under the umbrella of the .com big guns stunt or aid places like del.icio.us? The past few months seem to have been beneficial for Flickr at least.