Actionscript

This complete new tutorial is still in the process of being created. A few sections are already available with files to download, so be patient and don’t hesitate to already comment on the available sections or make requests for the incoming ones. A Dynamic Slide Show is quite a simple application but the more dynamic you want it, the more complex it gets. This tutorial will show you how to create a dynamic, flexible, and versatile slide show with AS3. The tutorial is divided in sections, each section covering a particular subject in the creation of a Slide Show.

Enables Rapid Creation and Delivery of Interactive 3D Content for Adobe Flash

Herzliya, Israel, July 28, 2009 – Revolver, Ltd. today announced the availability of FreeSpin3D™ for Adobe® Flash® CS4 Professional. FreeSpin3D is an Adobe Flash authoring extension that makes interactive 3D possible wherever the Adobe Flash Player is found, across all major browsers and operating systems. The updated release expands on last year’s successful launch of FreeSpin3D for Adobe Flash CS3.

If you haven't noticed, Flash CS4 Professional now supports the use of an External Library Path to reference class definitions in SWC files to be used, but not compiled, in your resulting SWF. What this means is that you can make "child" SWFs that are intended to be loaded into another "parent" SWF and have all, or most, of the class definitions limited to the parent SWF. This reduces the redundancy of those classes in each of the children saving you on bandwidth. Right now, however, Flash has a small problem when using such classes with library symbols.

I noticed an interesting consequence of having an incorrectly defined allowNetworking HTML parameter for one of my Flash projects: Full screen stopped working in IE.The problem was that I gave the allowNetworking parameter a value of "always". Sadly, this is not an allowed value. For some reason, because it was not recognized, on Internet Explorer it meant full screen also broke.The lesson here is that you need to watch your allow* parameters (i.e. allowFullScreen, allowNetworking, and allowScriptAccess). Each have their own set of allowed values which are unrelated to the other.allowFullScreen: [true | false]allowNetworking: [all | internal | none]allowScriptAccess: [always | sameDomain | never]My problem was mistaking allowNetworking values with those of allowScriptAccess. Silly me.