For the uninitiated, Processing→ is an open interactive media platform published on free software license via MIT by Casey Reas→ and Ben Fry→. Originally created as a learning tool, it is maturing through a Beta phase currently while winning tremendous support within the academic and design community. It appears to be emerging as the [tag]Sketchpad[/tag]↔ of the future. Sutherland→ would be so proud of his fellow alumni.

• Download Sample Chapters→ in PDF
• MIT Press→

For those in-the-know, this MIT Press release, Processing: A Programming Handbook for Visual Designers and Artists will be noticed on August 24, 2007. A substantial amount of the book is available in PDF format now. The free preview certainly suggests how tremendous and definitive this text is going to be. Take a peak at this inspiring passage from the introduction. It begins by describing the world view of Processing and the philosophy about software it epitomizes:

Software is a unique medium with unique qualities
Concepts and emotions that are not possible to express in other media may be expressed in this medium. Software requires its own terminology and discourse and should not be evaluated in relation to prior media such as film, photography, and painting. History shows that technologies such as oil paint, cameras, and film have changed artistic practice and discourse, and while we do not claim that new technologies improve art, we do feel they enable different forms of communication and expression. Software holds a unique position among artistic media because of its ability to produce dynamic forms, process gestures, define behavior, simulate natural systems, and integrate other media including sound, image, and text. (p. 1)

The introduction continues on to beautifully frame the pursuit of aesthetics through software. The free preview includes not only complete Table of Contents and Index, but also a very solid introduction to Processing and some of fundamental concepts. It’s enough material to function as an ideal free resource for getting started, while also leaves you thirsting for more.

Indeed, a more comprehensive review is forthcoming.

Adobe Integrated Runtime demonstrated by Big Spaceship.

This afternoon, Joshua Hirsch and Jamie Kosoy from Big Spaceship, here in Brooklyn, presented Building Adobe AIR Applications with Flash CS3 on the Adobe Connect presentation service. They did an excellent job of introducing the new capabilities of Adobe’s new desktop application delivery platform. In particular, they focused on how Flash CS3 can be used to compile AIR programs. Although still in Beta, AIR remains un-implemented in Flash CS3. The online seminar walked us through the tricky process of configuring for AIR development and introduce us to the command-line tools required to build and test AIR projects. However, Grant Skinner apparently has an extension set for Flash CS3 that assists with this process as we await Adobe’s full integration into the Publish Settings of Flash CS3. The links and notes of the presentation are posted here for reference. This post is likely to be updated and fleshed out as I process and try things out myself.

What is AIR?

AIR brings Flash and other web formats to desktop standalone applications. We should start to see more ‘downloadables’ once this catches on. Probably the best way to figure out AIR is to look at some examples on Adobe Labs→I’ve been a fan of kuler→ ever since I started following the Adobe Labs, and discovered Apollo, the codename for AIR. This is a great example of how being able to break out of the browser will encourage creative technology to engage with us more deeply.

Presentation Links

How to get started with AIR and Flash CS3

• Presentation Event Details
• About Adobe AIR
• AIR Developer FAQ
• Download AIR SDK
• Download FLEX Builder
• ActionScript 3.0 Language Reference
• Get the Flash Debug Player
• Get FlashTracer extension for Firefox
• Get Grant Skinner’s AIR Panel for CS3
• Big Spaceship’s Lab

Raw Notes from the Presentation

Here are the raw notes from the presentation. I’ll try to decipher them into more sense once I get my head around it all myself.

 airglobal.swc locations: MAC:    /Applications/Adobe Flex Builder 3/sdks/moxie/frameworks/libs/air/airglobal.swc PC:      Program Files/Adobe Flex Builder 3/sdks/moxie/frameworks/libs/air/airglobal.swc move and rename to MAC:    /Applications/Adobe Flash CS3/Configuration/ActionScript 3.0/Classes/playerglobal.swc PC:      Program Files/Adobe Flash CS3/Configuration/ActionScript 3.0/Classes/playerglobal.swc (you should make a backup of your old playerglobal.swc) AIR SDK: MAC:    Place all files in /Users/[you]/ PC:      Place files whereever you want. (I use c:AIR_SDK) Set environment variables: Right click "My Computer" Hit Properties. Go to the "Advanced" tab Click "Environment Variables" In "System Variables", under Path add path you put the sdk. If there is no Path var, you can add it. ADL syntax: adl myApp.xml Flash Tracer: After installing extension, Tools --> FlashTracer Click "Options" in the bottom right of the AddOn. PC Path MUST be: C:Documents and Settings[YOU]Application DataMacromediaFlash PlayerLogsflashlog.txt Mac Path MUST be: Hard Drive:Users:[YOU]:Library:Preferences:Macromedia:Flash Player:Logs:flashlog.txt If no Logs directory or flashlog.txt file is missing, you need to add them. ADT syntax: adt -package myAirFile.air myApp.xml foo.swf bar.swf icons videos etc