Category Archives: Flex

Two of the big events of the conference season, Adobe MAX and Future of Web Apps, finished up a couple weeks ago and now most of the recorded talks have surfaced online.

Adobe MAX 2009

Adobe TV has a MAX 2009 channel with a lot of content, with videos divided into three categories – Develop, Design and Envision.

Here’s some of the highlights:




Future of Web Apps

Carsonified have only uploaded a small handful of talks over the past few weeks but they’re all worth a watch. So far I’ve only found their London talks on their Vimeo channel, but the Dublin sessions have started to appear on the FOWA site.

Here’s what I’d go for:

I’ll update as and when more work their way online!

The big news out of Adobe MAX 2009 last week was all about mobile and the developments for the Flash platform on devices, the forthcoming release of Flash Player 10.1 and of course the announcement that Flash CS5 will be able to publish Flash files as native iPhone applications!

Flash on the iPhone

Here’s how they broke the news:

It’s a huge announcement.

Rumours of Flash running on the iPhone have been going around for over a year now, with Adobe and Apple ‘officially’ being in talks since November. The Flash team did well to bluff any developments when asked about it at Flash on the Beach this year, so clearly they were keen to save the big reveal for MAX as it deserves.

As you can see in the video, Flash CS5 will make it super-easy for developers to publish their Flash applications as a native iPhone executable, so simply it would seem, as changing a publishing setting at author-time.

This means developers don’t need to make any changes to their applications in order to run them on the iPhone (though presumably the APIs will be limited). It also means that existing applications won’t need to be rebuild from scratch (not even be completely refactored, as before) and can be distributed via the AppStore.

It doesn’t, however, have effect on viewing Flash in the Safari browser. This still cannot be done.

What Adobe have achieved is the ability to compile Flash as an iPhone executable to run as a native application – they haven’t created a Flash Player for the iPhone, or any way for the iPhone to interpret a SWF at run-time. They’ve made their files compatible, rather than the other way round.

There’s already some applications available in the AppStore, these are:

Adobe have created an Applications for iPhone Labs page demonstrating apps running on the phone:

Flash iPhone demonstration

There’s also an FAQ (and Developer FAQ) which goes through what can and can’t be done.

Mark Doherty has written about the announcement and lists some of the limitations that will be imposed, for example some typical features you might expect to work with, but won’t be available:

  • Microphone access
  • Camera access
  • Photo selection from file system
  • Contact selection from the address book
  • Cut/copy/paste
  • Maps

..actually quite a few limitations.

Ted Patrick is one of the Adobe team who developed some of the demo applications. He has posted an article on his blog with the four sample apps and included full source so you can see, as he says, there’s absolutely nothing special going on – it’s just simple AS3 cross-compiled to iPhone ARM Binaries.

Aditya Bansod has written an article for the Adobe Developer Connection which goes in the technicalities in a little more depth. He also has an hour-long episode on Adobe TV, taken from MAX, exploring the technologies:

Of course, it’s not news that Flash isn’t without sceptics. Not everyone is looking forward to the prospect.

Jeff Lamarche is an iPhone developer who has some very good points on being cautious when developing Flash for the iPhone.

He shares my opinion that you should avoid ‘hammer development’ principles and instead should choose the best tools for a platform. He says:

Flash has always been a compromise that takes considerable overhead to let you create applications that can run on multiple platforms, while feeling native on none and getting native performance on none.

He goes on to make valid points about performance when road-testing some of the applications, also noticing some inefficiencies and possible breaches of Apple’s guidelines.

Presumably when you create applications with the recommended workflow, with XCode, Interface builder and the iPhone SDK, developers are somewhat constrained by them – definitely with regard to the interface, visual components and interactivity. With Flash’s ‘back-door’ sneak of creating apps, these may be breached.

That being said, I haven’t had a chance to play with these applications yet (I don’t actually have an iPhone..) but even then, presumably these are apps for demonstration and are, as proven, purposely uncomplicated.

And as always Flash has its haters.

A comment on Mike Chambers’ post might be a bit knee-jerk and unjustified, but also hints as to some of the feelings that will no doubt surface if the AppStore is inundated with bad Flash apps and games.

Hopefully Apple won’t change their position on accepting Flash.

Flash on everything else

But not to forget – this was really the second big announcement of MAX.

The first announced that the forthcoming Flash Player 10.1 appears to run on pretty much every other smartphone and high-end mobile device on the market too. Which has a lot to do with new commitments to the Open Screen Project.

Ryan Stewart has a run-down of the news, which announces Flash will run on Blackberry, Palm Pre, Windows Mobile, Android and on Skyfire browser for Nokia Symbian OS (links via InsideRIA).

Google have joined the project, see the post on their blog and Adobe’s press release for more information.

At Flash on the Beach, Mark Doherty’s spoke about the improvements to Flash Lite and how advances in Flash technology outside of the ‘main’ Flash Player have beneficial effects overall, to the platform as a whole. One such advancement is that the new multi-touch and gestural events in Flash 10.1 will be completely available for non-mobile applications too.

Daniel Dura and Matt Bugbee‘s Multi-touch and the Flash Platform on Adobe TV discuss and demonstrate what can be achieved with these new events.

I’ve just noticed that InsideRIA already have a ‘Getting started’ primer for multi-touch Flash, too.

As I say, advances in one technology can propagate development in another. That said, Adobe have also announced that they are developing a lightweight Flex framework for mobile devices, called Slider.

Slider is a mobile-optimized version of the Flex 4 framework, allowing developers to leverage their existing Flex skills but benefit from optimised performance and a streamlined user experience for devices with less memory and slower processors.

There will also be a new set of user interface components.

Going full circle, a greater presence of Flash and Flex on mobile devices puts more pressure on Apple to adopt the Flash player for their Safari browser.

Hopefully some time soon, seeing this screen will be a thing of the past:

As Serge says, there’s lots of things to get excited about and it’s a great time to be a Flash Platform developer!

It’s been two weeks now since Flash on the Beach so I thought I’d collect all the links, slides, source code and videos from the various talks and demonstrations here in one place for ease of reference for whoever might need them.

I’ll try and keep this updated as and when I see more appear online, likewise if you see something I’ve missed – give me a shout!

I also thought I’d show off Artillery‘s excellent FOTB titles:

Day 0: Sunday 20th Sep 2009 (Workshops day)

Day 1: Monday 21st Sep 2009

  • Hillman Curtis (site) – Telling Stories
  • Joel Gethin Lewis (site) – Epiphany
    Lights On! in action

Day 2: Tuesday 22nd Sep 2009

  • Jeremy Thorp (site) – Hacking the Newsroom
  • Jennifer Shiman (site) – Using Flash for Your Cartoon and Comic Projects
  • Richard Lord (site) – Frameworks: The good, the bad, and the ugly
    View slides
  • Joel Baumann (site) – Numbers in Art
  • Paul Burnett (site) – More than Bending Pixels
    Source code and examples
  • Karsten Schmidt (site) – We make our own tools, and then they shape us.

Day 3: Wednesday 23rd Sep 2009

  • Andre Michelle (site) – Kling Klang
  • Serge Jespers (site) – The Flash Platform in a multi-screen world
  • Mark Doherty (site) – Contextual Application Development
  • Koen de Weggheleire (site) – PLAY with Vectors!
  • James Jarvis (site) – Live Drawing with James Jarvis
  • Jared Ficklin (Twitter) – Seeing Sound: Visualization in Nature & Code
    Source files
  • Ralph Hauwert (site) – Research Realtime graphics with Flash 10

Note: this post is a continuation of my previous two articles on FOTB: The Beach and Day Two.

Here it is – the third and final day of Flash on the Beach!

Contextual Application Development

Mark Doherty

Mark Doherty started the day filling in for the absent Serge Jespers, who would have been presenting ‘The Flash Platform in a multi-screen world‘.

Mark, known at Adobe as ‘the mobile guy’ gave what sounded to be a very similar talk, focusing on the contextual practices of cross-platform application deployment, rather than (I think) the development of those applications and the devices now available to us.

He outlined Adobe’s three vectors of innovation; Rich Internet Applications, the Cloud and Devices – exploring for each the opportunity to create Flash applications and introduced their newly adopted paradigm and tag line, ‘Single experience, multiple devices’. It’s their wish to enable full engagement of RIA experiences across any device and platform.

He talked about Flash Lite and improvements gained over the previous six years of development. Flash Lite is fast becoming a very powerful tool and it’s Adobe’s intention that it should take leadership of mobile application development over the likes of Java.

But the talk covered more than just mobile devices, for example Mark spoke about Flash for the television. On that he made an interesting point that would run the length of the talk, about the importance of being aware of platform context.

He pointed out that devices like the television are never intended to be turned off, so, similar to Grant Skinner’s note on applications behaving as good system citizens yesterday, these kind of applications need to be aware of memory usage and simply cannot have any memory leaks.

We need to redefine our notion of ‘Flash applications’ and readdress our habits formed as a result of only developing browser-based and non-persistent applications.

Another assumption that cannot continue is that we can get away with deploying an application that can simply dynamically resize for different screen resolutions. This is Mark’s idea of ‘contextual applications’ comes in.

Applications should be platform-aware, true – detect it’s screen resolution, but also be aware of it’s computational capabilities, graphics and data support, it’s interface mechanic and tailor our applications specifically to those.

We saw, which detected Mark’s touch-screen phone and served touch-screen games accordingly.

The New York Times have a collection of applications that think along the right kind of lines.

For the NYTimes, there’s the popular AIR desktop application, the Kindle version that serves the paper in PDF form, iPhone and Smart phones can browse the mobile website and there’s a version for the Chumby. Each platform offers a tailored experience and each has its own business model (some have paid subscriptions, some serve ads), but each is powered by the same service.

We saw UVLayer, a cloud-based virtual desktop and media sharing service funded by the Open Screen Project. UVLayer comes in two forms, visited in the browser or on a mobile device and the pair demonstrate this idea of contextual applications very well. The desktop is a place to administrate, manage an organise your media, but on the mobile the interface is remodelled and prioritise for the tasks you’d most likely want to carry out on a mobile – like watching and sharing those videos, photos and messages. It’s a different view of the same service.

The bottom line from Mark and Adobe now; don’t just scale or appropriate your application, recognise that platform, choose and serve content specifically for that platform and that context.

Connecting the Dots

Mario Klingemann

Mario Klingemann is a self-confessed ‘maths groupie’, likening his attraction to not being able to play the music, but loving the band.

His talk intended to reignite all of our lost love for maths, expelling all our bad feelings of the dry and boring maths taught in schools by delving into the beauty of geometry, the intricate patterns of computational design and the universal truth that only mathematics can behold.

He drew colourful metaphors of maths versus art, likewise of famous mathematicians and artists, before diving into number theory; his investigations into prime numbers with the Ulam spiral and Sacks spiral, before returning to geometric art with the tessellating and tiled designs of Islamic culture.

He offered some recommended reading on the various subjects, for example Daud Sutton’s Islamic Design: A Genius for Geometry, Robert Dixon’s Mathographics and Jay Kappraff’s Connections: The Geometric Bridge Between Art and Science.

Mario reunited us with cellular automata and algorithmic based systems to create some impressive visualisations. Making a connection with Flash, he plugged in Pixel Bender and created controls to alter system rules and introduced randomised variables to look for reoccurring natural visual phenomena, analogues of cellular or organic formations.

Another book recommendation – Stephen Wolfram’s A New Kind of Science.

Then he went on to talk about a bit of a game he had with Ralph Hauwert (UnitZeroOne) on Twitter, when he saw that he had sent out a Base64 encoded image message (explanation), where he tried to find if there were any other techniques he could employ to compress more complex images.

He applied a number of algorithms, encoding and compression techniques, then went on to exploit Twitter’s UTF-8 encoding and use Chinese characters, so it eventually ended up looking like this:

Mario Klingemann's encoded tweet

All very interesting, even though a lot went over most of our heads. He ran out of time eventually, but finished off the talk later in the day at the Jam Throwdown.

My colleague Adam Cousins joined me on this third day, he has written about Mario’s talk on his blog. He plans to write about rest in the coming week.

Union and MegaPhone

Colin Moock

Colin Moock‘s session looked at multi-user interactive activities and how he believes that multi-user activity is the future of all applications.

He questions how many of us would still be using computers if it were not for the Web, or an Internet connection. He thinks in the same way that the Internet adds value to computers, multi-user activity will add value to applications in the future, if not be the main use for those applications. In fact, that they’ll be pretty rubbish without it.

It’s something he’s felt for a while, he pointed to his Unified computing lecture of five years ago as an example as to how long he’s been thinking about it.

So Colin has developed the Union Platform. Currently in an alpha state, Union is a development platform, server architecture and protocol for creating such multi-user applications.

The Union platform breaks the complexity of multi-user application development down into a small group of digestible, familiar concepts; clients, the server, messages, rooms and attributes. It enables rapidly produced systems and supports Actionscript 3.0. Read more on the Platform Overview page.

We saw a demo created by Clockmaker, a 3D multi-user Tenori-on, deployed and ready to play with right now, and then he quickly coded a simple chat application which could send and receive real-time chat messages.

Writing it live, at one point Colin’s code had an error – of course with everyone watching there were plenty shouts from the crowd as to what was wrong. He said we just proved his point as to the value of introducing multiple users :) .

Then he talked about MegaPhone, a product that enables multi-player games and activities in public spaces by turning your mobile phone into a ‘universal controller’.

The idea comes from the assumption that pretty much everyone has a mobile phone nowadays (in the Western world, I guess), that we’re all ‘connected’ in the sense that we all have a device of this kind in our pocket – so why not enable us to converge with them and interact with each other, or with an interface in a public space.

MegaPhone enables any phone to work on any screen because it doesn’t require any kind of installation on the hardware, it uses the features that all phones share – dialling, voice and the keypad. It;s just a facilitator service, it’s not app that’s pushed onto the user – thus, it is the universal, and universally compatible, controller.

We saw the concept demos, a big screen Whack-a-mole that required lots of synchronised shouting and ‘Grabber’, likewise a relatively straightforward volume-controlled game where the user shouts in an attempt to get their character to grab various objects displayed on a big screen.

Colin is the core technologist at MegaPhone, so aptly he showed us some code. It is intentionally very straightforward, six or so listeners that refer to calling, hanging up, key presses and volume detection, all with custom event handling.

There’s contact details on the MegaPhone site to apply for a developer key now!

Jam Throwdown

Grant Skinner, Mario Klingemann, Julian Dolce, Andre Michelle, Jer Thorp, Joa Ebert

The Jam Throwdown premise is simple, six speakers have ten minutes each to do whatever they want – presumably to do the best they can to impress us. We were told to expect demonstrations of some of their best work or greatest failures, previews of as yet unseen apps or experiments, perhaps even some live coding – and undeniably every speaker succeeded in their task.

First up was Grant Skinner who demonstrated some physics and collision detection experiments he had been playing with, eventually combining them with the sound spectrum API to create a pretty cool dynamic audio visualiser.

Mario Klingemann continued showing the results of his image encoding techniques from his earlier Connecting the Dots session.

Julian Dolce demonstrated a handy tool to compile multiple FLA files, using Eclipse, by way of an ANT task.

I was probably the only one excited about this – generally I use a PC and I’ve heard you can write AppleScript to do this on a Mac, and Flex can do this anyway but Flash usually can’t. Good news is, it’s all available on his website and it can handle straightforward publishing, debugging, FLP files, intelligent error handling and is also available from the command line.

André Michelle extended his ‘Kling Klang’ talk on manipulating sound and run-time audio processing from earlier that day. He devised various algorithmic techniques for sound manipulation, creating delay effects and playing with feedback. There were some incidental sound experiments, a Tenori-on sequencer, more visualisations and a very cool graphical synthesizer tool.

View the slides on his site.

Jer Thorp showed us a piece of his work commissioned to design an accessible playground, but for which he employed very unconventional design techniques, largely by designing using Processing both in 2D and 3D.

Then came Joa Ebert, who had an incredible session on Tuesday which was already the talking point of the conference, anyone who hadn’t seen it had definitely heard about it.

Where everybody else had spent the full time talking and presenting their work, Joa just said “Hello,” queued some thumping dance music and immediately sat down to speed-code for the whole ten minutes, wowing us by creating a fully-realised 3D sound visualiser written in Processing.

Needless to say it was outstanding, not to mention that he afterwards revealed that he uses a keyboard without glyphs.

You can see the whole video on Vimeo:

Seeing Sound – Sound Visualization in Nature & Code

Jared Ficklin

With a DIY mindset, Jared Ficklin explored sound visualisation with and without code in a Maker Faire/Brainiac-style session.

Using smoke, fire, oscillators and costumes he worked through the physics of sound and waveforms and how they can be visualised.

We saw some of his work with the sound and sound spectrum APIs, visualisations he’s created in the past and a few by other artists such as Annika Hamann’s Fowl Owl and Robert Hodgin.

He offered tips and best practices on how to work with sound in Actionscript specifically.

Although the talk was very hands-on, he couldn’t do everything he wanted to do on stage. Especially set fire to things.

He had a enactment of a Rubens’ Tube, with a long hollow PVC tube filled with bean-bag polystyrene balls, passing a sound through the tube to watch the air pressure change the shape and form of the balls as it passed down the length, modelling the balls mimic the sound waves.

Do see the real thing in action, with fire, he showed us one he prepared earlier:


Joshua Davis

Flash on the Beach closed with an exceptional talk from Joshua Davis who explored the notion of Space. Not so much space as Astronomy, although apparently 2009 is the International Year of Astronomy, but of course with regard to design.

He talked about design technology, his approach to computational design and his past pioneering work with Macromedia Flash.

He talked about his work with other artists such as Stefan Sagmeister (as did Hillman Curtis on Monday) and Branden Hall, with whom he created Hype – an Actionscript framework for creating visual and generative art.

To see Hype in action, there’s some nice examples here and you can watch Joshua and Branden’s discussion with Carlo Blatz on Powerflasher’s blog.

Joshua went on to consider the notion of the physical design space, showing some work from various exhibitions, some interactive installations and his work with printed art.

As with every of the inspirational talks of FOTB this year, I’m going to cop out and say you really had to be there. Joshua is a funny guy and had everyone hugely entertained, as I’m sure you can imagine if you’ve ever seen him speak.

His presentation is also online now on his site (in zip format), which shows some of his great work.

See you next year!

And that was the end of Flash on the Beach 2009!

Needless to say again, it was a great conference. Honestly I didn’t know what to expect before going, this being my first year, but if offered so much more than I would have imagined it could. I go to plenty of other conferences, groups and conventions and this beats the lot.

John Davey insists that Flash isn’t a product, it’s a mindset – and Flash on the Beach captures that.

As for the organisation, it was flawless, and there was a huge amount of freebies thrown in too.

Thoroughly recommended, I’ll definitely be going next year!

Note: this post is a continuation of my previous article on FOTB: The Beach and continues with Day Three.

Day two of Flash on the Beach would prove to offer even more Flashy goodness than the first, with great talks throughout the day and wowing us every chance they got.

Elevator Pitch

3 Minute Wonders

The day opened with an hour of elevator pitches, allowing twenty solo attendees to individually take the stage for three minutes at a time to show their best work, idea, code or drawing – whatever they liked really. The idea being to give those brave enough an open audience to show off the coolest thing they’ve got.

And there was some cool stuff.

Mostly we saw people’s new business ideas and apps, lots of games and Actionscript experiments. A lot of them actually were projects that have been declared open source and some creators took this time to call freely for collaborators and testers. There was also a couple of generative artists thrown into the mix too.

All in all, given the talks that we ended with on Monday, what could have been an absolute incoherent shambles (as event runner John Davey did seem to worry about) came across as smoothly planned and well informed.

Probably the most useful project to note, I thought, was presented by Conrad Winchester called ASAXB – a tool that intends to put an end to the endless serialisation of XML to and from objects in order to handle your data with code.

Inspired by Java’s JAXB, it enables you to annotate code for marshalling and unmarshalling from Actionscript to XML. You don’t actually write the code that does the conversion, instead you give instructions to the marshalling system about how to package your object as XML and it does it for you. This is one of the open source projects that I mention.

Another talk was a really quick comparison between Objective-C and Actionscript 3, from Nick Kuh. Previously I’ve been a bit unsure about why Flash developers are either expected to (or keep banging on about) iPhone development – but somehow after seeing this I figured, it probably doesn’t matter. It probably doesn’t matter whether we should or shouldn’t be (or be expect to be) developing for iPhone or with Objective-C, ultimately, as this guy said – it’s just another language. In fact, the plus is that it’s an object-oriented language – so anyone with knowledge of OOP is halfway there already. So why not, eh?

Quick as a Flash

Grant Skinner

Basically, Grant Skinner is the man. You probably already know this, if not you should.

Grant’s talk was on optimisations for Actionscript. He went through a whole ton of techniques, practical examples, demonstrations and supplied code snippets from the most basic alterations to some pretty advanced trickery to provide ways to improve the speed of your code and relieve the CPU operating your applications.

Most people are aware of simple tips and best practices you can assert, declaring a loop length outside of the loop itself, collapsing literal values, using multiplication instead of division – those kinds of things – and Grant often blogs or tweets bits of code (he showed us some nifty bitwise tricks I’ve seen him post somewhere else before). But there was so much here, some stuff I’d not seen before and a lot I would never have even thought would really have any impact on performance – but wrongly so.

For the majority of his optimisations he provided timed tests and metrics for true comparison. Demonstrating the different ways of carrying out the same logic, highlighting areas that are easy improvements and black spots you should always avoid.

The optimisations weren’t only code-based either. He spoke about the other wages on performance, on-screen media (audio, video, webcam) and graphics (renders, filters, composites).

He also discussed the garbage collection of the current Flash Player and how to ensure there is an allocation for it to operate. He also considered the differences in the performance of the Flash player when running within the IDE, or standalone, or as a plug-in for the browser. There’s quite a difference.

This led on to his exploration of how to measure your own optimisations and to the tools that he has to offer to do so. See his PerformanceTest, FramerateThrottler and Janitor classes, to name a few.

There was a great depth to everything he said, he discussed qualitative and quantitative testing and the importance of benchmarking your tests.

Actually he made an interesting comment at the very beginning of the talk, stating the need for our applications to be good system citizens. As Flash matures and AIR becomes an ever-more solid desktop runtime, we can’t expect to hog the CPU anymore or for users to excuse that. It’s relates to my thoughts during Mike Chambers’ session with AIR on Monday, that I wrote about in my last post.

Anyway, the serious value of the talk really was in the code he provided and I’ve barely mentioned that. There was actually one hundred slides in all and I can’t hope to relay everything here. Fortunately his slides are already online, so read them here if you missed out. It’s such a great resource to have all those in one place.

Leaving the Sandbox

Joa Ebert

Grant Skinner is the man, because Joa Ebert cannot be human.

Joa’s talk was also about optimisation and began with some shared components of the last talk, but it soon became clear that his was ridiculously hardcore in comparison.

Joa took us down to machine code-level to analyse optimisations, scrutinising the compiler mechanics and the processes it performed during compilation.

He demonstrated the first of his frameworks, AS3V, a code-validator like no other for Actionscript 3. Born out of unhappiness with the current compiler and other code validators, AS3V will generate warnings and offer optimisation tips upon detecting exactly the kind of code that Grant talked about improving earlier – not just code errors.

For example, he talked about loop invariants, a often-encountered situation where a value is declared inside a loop even though isn’t changed with every iteration. Of course, this code compiles and executes, but needlessly takes longer to process (having to instantiate a new variable each time). His validator, available as an Elipse plug-in, detects those kind of code inadequacies and alerts the user at author time. It points out code that will run slowly, not only code that won’t run at all.

The tool looks for the breaking of coding guidelines and best practices, as well as opportunities for runtime errors – where compilers of course, only look for compilation errors.

Turns out Joa was only getting started at this point. He spoke about another framework he developed during ‘a week off’, called Apparat. This is a monolithic framework behind a number of other tools he then went on to talk about, all concerned with optimisation.

The first was TDSI, TurboDieselSportInjection! an optimisation for Alchemy – you can see some examples here.

Second there was Reducer, which reworks the JPG compression for SWF files to make them an incredible ten times smaller at 100% quality compression, or obviously even smaller at lower percentages.

Then he demonstrated Dump, a disassembler that looks at machine bytecode for the purposes of debugging and can also be used to generate inheritance graphs and UML diagrams from compiled SWF files!

Finally he presented TAAS, ‘Three Address Action Script’, which is an optimiser for the Actionscript compiler rather than the code.

Joa wrote this program to find inefficiencies in the compilations process, for example finding opportunities to rewrite algorithms, perform dead code elimination, some relatively ‘straightforward’ stuff like single static assignment and in-line expansion – and even to make use of functions that Adobe have written into the compiler but don’t actually use!

He showed that when performing calculations on to ints, the compiler converts the values to Numbers (and back again) in order to use the Number calculator even though there is an int calculator available.

Ultimately, he compiled with his optimiser and the performance increase was simply amazing - calculations and transformations faster than anything I’ve seen before, and I’m sure faster than Adobe have ever seen either. I cannot see why he doesn’t work for them. It’s not released yet, but you can follow updates on his blog.

Joa Ebert by C4RL05 on Twitpic

Joa Ebert by C4RL05 on Twitpic

“Oh yeah,” he then said, “I’ve got one more thing” (this was after plentiful applause and people were already getting ready to leave).

As if he hadn’t impressed us enough, Joa then showed us, in seconds, that he’d written two more new compilers himself – one that compiled C# directly to a SWF file and another that compiled Java to a SWF file.

I kid you not. Then came a lightning fast fly-through look at how they work (that probably no-one understood), some proof it was live and working and real – and he deserved the standing ovation he got.

Have a look at how many wowed tweets immediately followed his session, including those from some speakers who were present. It really was something.

His slides are also up online now, they’re over on Slideshare here.

More than Bending Pixels

Paul Burnett

After lunch I attended Paul Burnett‘s session on Pixel Bender, a tool I’m still yet to use.

Honestly, I didn’t really know much about it before I turned up, of course I’d heard about it and had seen the getting started demos everyone has seen and I think a lot of people were at the same situation there – keen to see what it can do and hope to see more than just the basics covered. It was packed.

So he started with those basics – the spherize, twirl and tangent flip filters, but quickly ramped it into something interesting. He shared with us the thinking behind the tool, how some of the mechanics work.

Pixel Bender actually runs as a different thread to Flash (now I think about it, they mentioned this at Monday’s Town Hall meeting when asked about threading), so any processing it performs, regardless of the task, does not impact on the speed to which Flash performs. This can be leveraged in interesting ways (more later).

We looked at the anatomy of a Pixel Bender plug-in – the PBK kernel file, the code of which you can edit and how to run this file in Photoshop. Later, the PBJ file which is the compiled extension used within Flash.

Pixel Bender plug-ins are developed within the Pixel Bender Toolkit, essentially another IDE which comes with Flash CS4. Apparently though, it’s hidden away somewhere (in a utilities folder?), perform a search and find it for yourself.

Within the toolkit we dissected a filter script, discerning the role of parameters and how to manipulate images on a pixel-level with the evaluatePixel() method. Ultimately we threw a plug-in into Flash and got something running – basic shades and blends, how to duplicate an image, return two versions, how to use multiple input images and how to write straight from Pixel Bender without supplying any source at all.

This is all very cool anyway, but Paul mentioned that it’s not only image manipulations that Pixel Bender can perform, essentially it’s any kind of data.

He showed us how to send a sound file through a filter, with a simple plug-in that looked an instance of a Sound class (sent as a ByteArray) and performed a similar function to the duplication of an image, by returning itself and the sound at a position slightly earlier, creating a delay effect.

In the same way that a Pixel Bender filter looks at an image pixel-by-pixel and returns a stream of modified data back out, the sound byte array is considered the same. He basically listened for a data change event on the instance of the filter, passed that into a new Sound object (with a bit of a buffer) and played it in real-time. Very cool.

There’s far more simple stuff you can do – he demonstrated a six channel mixer that received six sound files, contained six parameters – a value to determine the volume of each channel – and passed them straight back out after a simple transformation on the amplitude, easy and very responsive.

Persisting that ‘data is just data’ and Pixel Bender doesn’t care what it receives, he then sent some pure numbers to a filter to perform simple trigonometry calculations.

At first this might seem a little needless, seeing how Flash can perform these calculations after all, but then you recall that these processes are running as a different thread.

He provided us with an example that called for some heavy calculations to be processed whilst simultaneously playing a video clip on the stage. With normal Actionscript the calculations caused the video to hang and the framerate to drop, but by utilising Pixel Bender’s own thread and mathematical processing power, by sending the calculations there instead, Flash is left free to play the video as in any normal instance whilst Pixel Bender does it’s own thing – it just reports back when it’s done.

Then David Lenaerts of Away3D joined Paul on stage to show some impressive demos of Away3D which has adopted Pixel Bender for lighting effects and texture mapping. Some very nice reflections, lighting effects with fire and ambience and an example with a human face that renders sweat, scars and frowns all with the tool. The examples are here on David’s blog and here on the Away3D blog.

Paul has now put this slides and source online on his blog.

Unconventional Web applications


For the first of the two inspirational talks of the evening, Dublin-based Contrast, in the form of Des Traynor and Eoghan McCabe, spoke about creating unconventional applications. They explored the notion of conventions – on the Web, in design, in life – praising the importance of following them and the ramifications of those who do not.

They discussed the problems of only following conventions; the restriction they put upon innovation, the idea of being lazy by essentially following suit as a rule of thumb, and the decreased marketability of products that can only follow a trend.

They were well versed in product design and consumer technology and pointed to some of the champions of unconventional design, the success stories of those that broke the rules. Apple with the iPhone, for example, who launched a radical mobile device in one of the hardest markets to penetrate; the Dyson vacuum, a product in a saturated market which is bottoming-out and the lowest price wins (which is the worst way to win); and the Nintendo Wii, which swam against the ever-rising tide of hyper-real graphics and enhanced performance and instead reinvented interactivity, engagement and had some fun.

Then they took these ideas to the Web, prompting a challenge to conventional wisdom on layouts, the sign-up process, the home screen and even copy.

All their points were valid, but I couldn’t help but feel that their information was a bit outdated. Especially with regard to the current state of the Web – especially, unfortunately, toward rich media, Flash sites and RIAs.

Their critique of Web design for example, seem to dissect the kind of HTML sites that were popular four or five years ago, where people weren’t daring to break a two- or three-column layout, with an inverted ‘L’ navigation and probably Times New Roman. Back then of course their ability to do so was somewhat limited too. But we’re at a cutting-edge Flash conference, where everyone knows what you can do with websites now and we’ve been treated to amazing demonstrations throughout the whole day, so it felt like these guys were equally a bit behind with the current state of play.

They showed a site as an example of the kind of rule-breaking they want to see, but it was very basic – an almost entirely static one-page Flash website actually with the kind if obfuscating highly-convoluted navigation mechanism that we look back and frown upon. One that overuses Flash for the wrong reasons.

At one point Des actually said ‘the Web is moving toward multimedia now’ and there were a few suppressed sniggers in the crowd, but then earlier in the talk they had openly admitted to not really knowing much at all about Flash, it’s not their field, so no-one held it against them – especially since the rest of the presentation up to this point extremely insightful.

Choose Your Own Adventure

Craig Swann

Craig Swann‘s session was like no other. What started as a journey through his childhood from early coding days and finding his way onto the Internet, turned into a profound and existential exploration of life, success and creativity.

I honestly can’t relay his talk, how he took us from his college years to the Grateful Dead, via a trip on liquid acid and praying with Santana, to exploring cymatics, to founding his agency, and what happens when you run polygraph tests on plants or get Buddha monks to talking to rice and water.

(All of this happened).

Bottom line from Craig: you choose your own adventure – “We are what we think”, inspiration drives opportunity.

End of day two!

We gotta get out while we’re young.