define('DISALLOW_FILE_EDIT', true);{"id":173,"date":"2009-04-29T17:42:03","date_gmt":"2009-04-29T22:42:03","guid":{"rendered":"http:\/\/www.unfocus.com\/?p=173"},"modified":"2009-10-27T17:36:59","modified_gmt":"2009-10-27T22:36:59","slug":"as3-unfocushistorykeeper-in-svn-trunk","status":"publish","type":"post","link":"http:\/\/www.unfocus.com\/2009\/04\/29\/as3-unfocushistorykeeper-in-svn-trunk\/","title":{"rendered":"AS3 unFocus.HistoryKeeper in SVN trunk"},"content":{"rendered":"

I added an initial round of AS3 files to the SVN trunk to make HistoryKeeper more accessible from Actionscript 3.0. If you are feeling adventurous, feel free to check it out<\/a> of the trunk<\/a>, and give it a try.<\/p>\n

There is also a small resurrected Actionscript to Javascript communicator (eh, it’s totally new actually, but I got to use old knowledge!). The theory is that if you use fscommand<\/a> to send simple strings to Javascript, you save on Flash setting up a lock to wait for a Javascript call to return a value or finish executing, which should conceivably avoid a short hiccup in the Flash Player. I’m not sure if there’s a real world benefit or not yet – one day I might get around to testing to make sure. At the very least, this framework will make it easier to setup fscommand, since it takes care of creating the javascript snippet for you. After that, it will simply eval<\/a> whatever you put in the command argument (unless it’s a simple function on window, then it’ll just execute that).<\/p>\n

Any comments are welcome. Please note, these classes may change quite a bit, they’re not to be considered stable (though the API probably is, there’s not much there really).<\/p>\n","protected":false},"excerpt":{"rendered":"