I am really excited about the FITC San Francisco Flash conference, coming up in about a month. First, it is a FITC conference which means all of the top Flash designers and developers in the world will be speaking and hanging out. But more significantly, it is FITC in SAN FRANCISCO, the first major Flash conference in San Francisco in quite a while. As you probably know San Francisco is the home to the Flash authoring and player teams, as well as some of the top creative agencies and developers in the world. This makes it an amazing opportunity to not only see some of the coolest stuff going on in Flash today, but also hang out with all of the people making it happen.

I have finally released the source code for my PewPew game. PewPew is a game I started working on over a year ago to help me understand what optimizations would be required to convert a web based Flash game to run on the iPhone. I had planned to release the code earlier, but a little hiccup around iPhone support delayed that. Now that Adobe AIR for Android is in public pre-release, and I have had time to comment all of the code, it is ready to be released.

I have just posted a new release (.93) of as3corelib. The corelib project is an ActionScript 3 Library that contains a number of classes and utilities for working with ActionScript? 3.

You can view a complete list of changes in the change list (items 75 - 106).

You can download the updated SWC and source from the project’s download page.

Thanks to Christian Cantrell for helping build the release.

For today’s myth, I want to cover one that has its roots in some fundamental misunderstandings around video technologies. That is the idea that H.264 Video (deployed via the HTML5 video tag) will kill Flash. This is a more recent meme, which has spread with the growing awareness of the forthcoming HTML5, but is unfortunately based on some fundamental misunderstandings about Flash, video capabilities, and the web in general.

First, we need to clarify a few things. H.264 is a video codec and not a player. It is a way to encode video. In order to view an H.264 encoded video, an end user must load it into a player such as running in Flash Player, Quicktime or VLC. Flash Player is a full featured multimedia runtime which supports a wide range of multimedia formats including H.264 (as well as other video codecs). Developers can create Flash content that can load and play H.264 encoded video (as YouTube does).

As you probably noticed, yesterday Adobe ran some ads expressing its thoughts on the importance of open markets. I think Adobe’s position is best summarized in an open letter from Adobe’s founders, John Warnock and Chuck Geschke:

When markets are open, anyone with a great idea has a chance to drive innovation and find new customers. Adobe’s business philosophy is based on a premise that, in an open market, the best products will win in the end — and the best way to compete is to create the best technology and innovate faster than your competitors….

Today I wanted to look at a more recent misperception around Flash. That is the idea that Flash cannot work on devices with touch screens. If you know your Flash history then you will probably find this a bit ironic, considering that Flash was originally created specifically for tablets with touch inputs. Regardless, lets take a closer look at this myth.

The myth began with the publishing of this article. I have already covered this topic in another post, but I wanted to address it again as it seems to have spread lately.

This is one of the most prevalent misperceptions associated with Flash. Basically, the myth is that Flash uses an inordinate amount of CPU compared to other, similar technologies.

Before looking in more detail at this misperception, I think it is important to point out that when one makes the statement “Flash is a CPU hog”, they are making a comparison of Flash CPU usage to some baseline. This then begs the question: Flash uses a lot of CPU compared to what? By comparing Flash CPU usage to other similar technologies and content, it becomes clear that Flash CPU usage is not excessive for the type of content that it displays and executes.

Interview with Kevin Lynch at Web 2.0 conference in San Francisco. Covers Adobe, Flash, innovation, HTML 5, thoughts on the direction the web is moving, competition, and omniture. Highly recommended.

You can view the video on YouTube

A little over a week ago Apple released a new draft of their iPhone developer program license which contained the following clause:

3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).

I have just posted information about FlashCamp San Francisco, a free developer / designers event that we will be holding in the Adobe San Francisco Office on Friday night, April 16th. This will be similar to the other world wide FlashCamps going on this spring, with this event focusing on Flash Player 10.1, Flash CS5, Flash Builder and Flash mobile development.

Register for FlashCamp San Francisco

From the event page:

FlashCamp San Francisco is a free one night event hosted by Adobe covering everything you need to know about about the latest Flash Platform tools and technologies, including Adobe Flash Player 10.1, Adobe Flash CS5, Adobe Flash Builder 4 and mobile design and development.