Home  >  Standards  >  blogs

Adobe Open Screen - It's getting there.

AddThis Social Bookmark Button

RJ blogged a bit earlier, but I thought I'd share a couple of my thoughts too. I guess we all knew this would come eventually, Flash is more open thanks to the Open Sceen Project.Here's the skinny on the what new licensing entails:

- Removing restrictions on use of the SWF and FLV/F4V specifications
- Publishing the device porting layer APIs for Adobe Flash Player
- Publishing the Adobe Flash® Cast™ protocol and the AMF protocol for robust data services
- Removing licensing fees - making next major releases of Adobe Flash Player and Adobe AIR for devices free

The biggest implication of this is that it's now possible, and likely already underway, to port the Flash Player to other devices such as phones and other personal electronics. What was your second reaction to the iPhone? Mine was "does it run Flash?" and I don't think I was alone. Actually could we get in on the Blackberry first...maybe some of my fellow Canadians are already on it. Let's hope so:)

For large organizations and governments just the possibility of creating an alternative runtime is big enough benefit to make this announcement noteworthy.

Let's keep in mind that even though the spec is open and free that doesn't mean it's small job to recreate the Flash Player, after all some of the brightest minds in the industry have been working on it for over 10yrs. Most attempts to recreate it will be slower, bigger and buggier...especially in the early days. The flip side is that the bright mind of the Flash community can now look through the spec and provide feedback to Adobe.

One thing to note as Dion points out is that the license hasn't been published yet, so let's hope there's no surprises in there.


Unfortunately, when I looked into the details, there wasn’t much to see. The claim was that the FLV/SWF/F4V binary formats will be Open, and there will no longer be the restriction that said you can’t RUN the code.

The problem was that there was no license to go along with this claim, which means that we can’t actually do much with it yet. Adobe isn’t more “Open” today than it was the day before the announcement. This will hopefully change very soon when we actually see the license, and hopefully see even more.

I know there a lot of critics out there saying this isn't good enough, but it's a step in the right direction. I'm sure the license details will be forthcoming.

Like giving the PDF spec to ISO, Tamarin to Mozilla and open sourcing Flex Adobe is making great strides at becoming more open. It's great to have momentum in this direction from one of leaders in the RIA space. It's going to be a while before the impact of this is felt, building new runtimes and getting them distributed just takes time. It's going to happen though.

Comments

2 Comments

Chris Brind said:

Good post, I am especially looking forward to more devices supporting Flash.

My only concern there is that it will have the same barriers as J2ME.

To start with, with Blackberry for instance, you have to do something to your J2ME archive to get it to deploy to your RIM device. I would hope that with Flash it will just be a matter of pointing your device at a URL containing a SWF or using some simple management tool to load your SWF on the device via USB.

Also, how will the Flash Player expose the device specific capabilities? Will we get in to the mess of having to create different SWFs for different devices or will there be an abstract layer and/or device capability introspection? Both approaches have their swings and roundabouts.

If I were to choose an approach I would develop a range of APIs that abstract various device capabilities and have these deployed with the Flash player on the different devices. It's easy enough to check from within a Flex app if some Class or is available or not so that would be a very simple way for checking if a device has a specific piece of functionality.

Next, will vendors be implementing Flash Player for the devices, or will a device specific VM come from Adobe? If so, how will Adobe choose which devices to support first?

So it's a fantastic thing, but there's still a load of questions to be answer.

Personally, I would love to be able to write a Flex app and deploy it to my Blackberry then hook in to the on board capabilities such as GPS and be able to make calls to servers on the internet. I can see the potential for a lot of great enterprise applications.

To the industry I say please, keep it simple and try to standardise ahead of Flash player randomly appearing on different devices.

Chris Brind said:

update: I just read about the device porting layer APIs. =)

Leave a comment


Type the characters you see in the picture above.

Poll: ECMAScript Reaction

The ECMA organization recently decided to stop work on ECMAScript 4 and begin a new version, tentatively described as ES "Harmony." How would you like to see this affect the evolution of ActionScript?

Vote | View Poll Results | Read Related Blog Entry

Tag Cloud

Related Books

Development Series

Get an overview of the tools and technologies that work together to allow developers to build Rich Internet Applications (RIAs) quickly and easily.

Anatomy of an Enterprise Flex RIA

Archives


 
 


Or, visit our complete archive.  

About This Site

Welcome to the premiere community site for all things RIA sponsored by O'Reilly Media and Adobe Systems Incorporated.

About Us
Meet the Experts
Meet Our Contributors
Send Us Feedback