Ecma just recently announced that the long standing EcmaScript 4 proposal is dead in favor of focusing on the EcmaScript 3.1 proposal. According to the announcment, they will eventually work on EcmaScript 4 again, but under a revised plan. ES4 as we know it in ActionScript 3 appears to be dead. Specifically concepts like namespaces and packages will be dropped entirely.
So what does this mean for ActionScript 4? Will Adobe actually remove features to keep it compliant with Ecma?
Ecma has been split for a long time on the direction of EcmaScript. there are two camps, Microsoft has been pushing the EcmaScript 3.1 arguing that EcmaScript 4 is too much for the web (whatever that means). The other camp is lead by Mozilla and Adobe pushing for the evolution of EcmaScript with the ES4 proposal. I agree with the idea of EcmaScript Harmony. Ecma should be unified. But its unfortunate that the “standard” is now behind the ActionScript implementation.
I’ll also be announcing the AIR Distribution Kit open-source project. This is a ActionScript 3 library for creating update functionality within AIR applications and for creating custom browser-based install applications (otherwise known as install badges). You can see more information about this project on my labs page. I just started this project, so there might be some bugs. Check it out and let me know what you think. Please let me know if you see anything you wish working differently or what features you’d like to see added in the future. If you’re interested in assisting with the development, please contact me.
I’ll be speaking at FlashBelt again for the fourth straight year in June. I’ve spoken at this conference every year since I moved to Minneapolis in 2005. It’s a great conference that brings in both local and national attendees. My session is titled Distribution and Installation Strategies for AIR and will cover the following:
Flash and Flex developers have been spoiled by the fact that most of our applications are distributed over the internet through the browser and Flash Player. We didn’t have to worry about installation or updates within an application. This session will walk you through the process of building a custom badge using Flex that handles the installation, update and launch of your AIR application from within a browser. We’ll also look at how to implement an update feature within your Flex AIR application so your users can always have the most recent version of your application.
We were talking about debugging Flash/Flex applications inside the browser the other day at MN.swf Camp and I mentioned that someone had created something called FlashBug that interfaced with Firebug. I’d never really looked into it much, but I knew it existed at one point. Well, it turns out the link to that is broken. So I did a little digging and found that the interaction with Firebug is super simple. So I decided to create a custom Target that works with the Logging framework in Flex. The following is an example of how to use this target:
var logger:ILogger = Log.getLogger("myLogger");
var logTarget:FirebugTarget = new FirebugTarget();
logger.info("info from flex");
logger.error("error from flex");
logger.warn("warn from flex");
logger.debug("debug from flex");
Download the FirebugTarget class here.
Since I’ve been doing more AIR development lately I’ve had a need to create and modify SQLite databases. I’ve used Microsoft SQL Server and its tools a lot over the years, but I haven’t used a wide variety of database programs. I’ve always been a big fan of Altova’s product line, so I thought I’d check out DatabaseSpy. This is their database editor and I must say I like it a lot. I sugest you try it out. Here is how I got it to work with SQLite:
Have you ever wanted to actually compile XML data into your SWF before? I wanted to do this to embed the build version into my Flex appliction. The version was stored in an XML file and updated during the build process. But I wanted the version to actually exist inside the SWF in order to decouple the depandancy on the external XML file at runtime. This way I don’t need to worry about the XML file not loading or getting seperated from the SWF. The version will always be there. Here is a simple example doing this in Flex.
MN.swf Camp sold out in less than three days. We had to limit the attendees to 100 because of space limitations, however, we are currently exploring other venue options. If we can secure a larger venue then we will reopen registration. I suggest you sign up for the mailing list on the conference home page so you can be alerted if registration opens again.
MN.swf Camp is a one day conference in Minneapolis focusing on the Flash Platform for programmers. Its being organized by the MN.swf User Group and FlashBelt.