Archive for May, 2007

Now Available: ActionScript Virtual Machine 2 (AVM2) Overview

The ActionScript Virtual Machine 2 (AVM2) Overview document is now available on the newly revamped ActionScript Technology Center. It’s a bit of a techie document, but it is interesting for folks that are working with the open source Tamarin project. The overview describes the instructions, associated data structures, and file format supported by the AVM2.

We reorganized the ActionScript dev center so the information was more logically grouped into “getting started”, “migration” and “more details”. It’s still quite long, so I consider it to be a work in progress 😉

p.s. Yes, the SWF and FLV file format specification is also coming soon. There was some work required to update the EULA language with the Adobe wording and cleaning up some of the poorly worded terms which took a while to hash out and get approved. The basic structure is the same — the spec is for figuring out how to output SWFs. I’ll post an announcement as soon as it is online.

(tiny) clarification on bi-directional text support in the next Flash Player

I see that my fellow product manager, Matt Chotin, has “committed” support for bi-directional text support in the next major version of Flash Player on the Flex Components Yahoo group. 😀

Don’t worry, I’m not taking it back. Be assured that bi-di is a long requested capability that we do indeed intend to support in the platform. But I thought I’d clarify a bit since people will want more details.

First off, as everyone knows, the text layout engine in the current Flash Player does not support bi-di. There are plenty of ways that you can simulate it for certain use cases, but we acknowledge that it falls well-short of what our developers need. To address the shortcomings and limitations, we are improving the text layout capabilities in the next Flash Player so that at a low level it will enable support of bi-di and complex text in your applications. The new low level text framework will be used to build text components (probably a library of text components) with greater functionality than what we have today.

Want to help us figure out what we should be working on? Are there components you would expect Adobe to provide? What types of applications are you trying to build? Let us know what your requirements would be for improved text layout, bi-di or other things you’d like to do with text in your content and applications that you can’t do today.