Category Archives: swfobject

Flash is dead. Long live the internet.

Posted on by

When I was in high school I didn’t own a computer. I used to read the occasional Popular Mechanics magazine and would linger for a while on the articles about the internet or HTML, fascinated by this new technology that I had barely even used. I don’t know why, but for some reason I’ve always been drawn toward computers, but more specifically, computers connected to other computers. Whether it was playing a video game online or browsing through the millions of websites, I could always spend hours every day in front of a computer soaking up information and experiences, interacting with people on the other side of the world.

Soon after I bought my first computer I started building simple websites. I had all of the best animated gifs you could find, along with those awesome water ripple java applets and whatever other bells and whistles I could find. It was awesome. I wanted to push the boundaries of this new thing. To make something unique that nobody had seen before. This led me to Macromedia Flash 4. My new hobby slowly taught me how to program, and over time I got pretty good at it. Eventually I landed in New York City and found a job at a tiny little web design shop, building websites for big corporations and loving every minute of it.

During this time the internet was recovering from the big crash at the end of the 90′s and as browsers slowly evolved, so were the websites we were building. But browsers were slow to update back then, so Flash filled a need to move faster and give us more options to explore and new technology to use (and abuse!). Around this time I wrote a little javascript utility to detect the presence of the Flash plugin and conditionally inject Flash into a website or not, and I watched as it grew over the years and became one of the most used utilities on the internet.

Flash was huge. Everyone wanted a flashy website and the only way to get one that any meaningful number of people could see was to use Flash. As browsers struggled to keep up, Flash charged ahead allowing us to build some truly amazing websites. Admittedly, there was some abuse of this technology, but we still charged ahead, trying to discover and build the next generation of user interfaces. Most older companies still thought of the internet as just another medium to advertise on. They wanted a flashy website to show off to their investors and clients and cared less about building something useful. The ubiquity of the Flash plugin made it an easy choice to build these new kinds of websites. We weren’t held back by the limitations of HTML any more, and that let us all explore wild ideas and try things that wouldn’t be possible with HTML or Javascript for years to come.

But now, years later, the browsers are catching up. Mobile devices are becoming more important than desktop computers (a trend I expect to continue for years to come). As more people use the internet in their day to day lives, businesses have realized that having a useful website is more powerful than just a flashy animated advertisement.

A few months ago I noticed that SWFObject usage on the top 10,000 websites was declining for the first time ever (I believe usage peaked in the summer of 2010). Last week, Adobe announced that they would halt development of Flash player for mobile devices, and refocus their efforts on HTML. Since this news was announced, I’ve seen many sad and nostalgic tweets from friends and colleagues. Some seem to be taking the news better than others, and it’s understandable that some people are sad to see Flash go. But it’s important to remember that no single technology is responsible for this awesome thing we call the internet.

This brings us back to my younger self sitting at home in Arizona playing with Flash and Photoshop, building new things. I’ve always loved making things, and I suspect many web developers feel the same. The pleasure of making something great is what drives us, not a specific technology. So don’t be too sad about Flash evolving, or even dying. Just keep making awesome things with whatever tools you have at your disposal.

Discuss this post here: http://news.ycombinator.com/item?id=3227994

SWFObject now available on Google AJAX Libraries API

Posted on by

I’m happy to announce that SWFObject (version 2 of course) is available from the Google AJAX Libraries API.

What does this mean to you, the average user of SWFObject? It means you no longer need to place a copy of the SWFObject script on your own web server, and can instead link to the copy hosted on Google’s servers.

If you are unfamiliar with the AJAX Library API, you can find more information on the Google code site, or continue reading below for some simple examples to get you up and running quickly. SWFObject may not be in the docs on the AJAX Libraries API site yet because it was just added recently, but the team is working on the updated docs now, so check back later if you don’t see the SWFObject specific information.

Now for the business: I imagine that most SWFObject users most likely only use SWFObject and none of the other libraries hosted on the AJAX Libraries site. So here’s a direct link to SWFObject v2.1 that you can simply place on your site, and that’s it:

http://ajax.googleapis.com/ajax/libs/swfobject/2.1/swfobject.js

Yep, that’s it. Just replace the path to your local copy of swfobject.js with this one and you are done.

Another option is to use the google.load call which is documented here.

SWFObject 2.0 released!

Posted on by

After months of work, we are pleased to present SWFObject 2.0.

The project has moved over to the code.google.com website instead of my blog, so go over there and check out the docs and consider upgrading, as the new version is a lot more flexible than v1.5.

I’d like to give a huge thank you to all of the people who contributed and helped us test out the new release, those no longer with us, and of course to Bobby who is easily the biggest contributor to this new version (and has a new design up on his blog!) and has kept the project pushing forward at a good pace.

Moving foward, we’ll be continuing to work with Adobe to get the word out about SWFObject 2.

SWFObject 2.0 Beta

Posted on by

Today at Adobe MAX I’ll be giving a presentation with Michael Williams on the next version of SWFObject (previously the SWFFix project). As most of you probably know, I’ve been working on a project with Bobby van der Sluis and Michael Williams (From Adobe) that was going to become the de-facto standard for embedding Flash/Flex content. Well we decided that we didn’t like the new name all that much, so we are adopting the SWFObject name for the project.

The new version is a complete rewrite from SWFObject 1.5, so we’ll need lots of testing before we officially launch it and replace the older SWFObject and UFO scripts, and since we have Adobe involved, they will be including this embed system in the Adobe authoring tools in the future.

The SWFObject project is moving to Google Code, where you can download the source from svn, grab the latest build, or file bugs or read documentation.

I’ve also created a new Google Group for SWFObject support questions and discussion.

If you are at MAX today, our presentation is at 2:45pm in room W-196c and it’s called “Flash Detection and Embedding: An open source solution”.

If you can’t make it today, we’ll be doing it again tomorrw (Wednesday) at 11am in room W-185d.

The SWFFix alpha is up

Posted on by

Bobby put up the SWFFix alpha earlier today – I’ve been at the Ajax experience (with no wireless internet access, wtf?!) so haven’t had time to put together a post about it, but here’s a quick one.

We also announced that we are now working with Micheal Williams from Adobe – the author of the Adobe Flash Detection kit to make sure SWFFix can cover all the bases and be used by anyone. Very cool!

Go check out the dev blog and grab the files, then read the docs and try it out. Feedback is very welcome, so soak it in and let us know what you think.