http://www.learningactionscript3.com/2007/12/14/sending-data-from-avm2-to-avm1/#more-29
It will be quite interesting to see how Captivate 4 addresses this issue. I heard from a very reliable source (as reliable as it gets…but that’s all I can say) that Captivate 4 (if that’s what the next version is going to be called) will have the ability to publish swf’s to AVM2/ActionScript 3 format. There are going to be lots of instructional designers/developers who rely on Captivate/PowerPoint as their sole tools who will be in a world of hurt if they find out that their old content is not compatible with newer AVM2-based content without a workaround such as the discussion in the link above. I’m sure Adobe has to realize this and the Captivate folks in Bangalore are going to come up with a slick/transparent way of handling this….
One Comment
nice link, i like the way they described the process.
i created a Captivate-specific example of AVM1-AVM2 communication if you’d like to see it:
http://pipwerks.com/lab/captivate/loading-in-AS3/
i explained the pros and cons in a blog entry, but i never got around to explaining how to do it because it’s such a complicated process. the link you just provided makes it look so simple!
i think one of the key differences between the example in that article and what’s required for a Captivate-to-AS3 solution is the need for a third SWF (a ‘proxy’ SWF) since you can’t add ActionScript directly to a Captivate project’s timeline.
i’m on pins and needles waiting to find out what features will be in Captivate 4… i hope a rewrite of the underlying AS code (with support for AS3) is in the plans!
cheers
- philip