David Ehlers

Nice tutorial of full screen flash setup here over at gotoandlearn.

Physics engine for flash in 2D - Box2DFlashAS3 is an open source port of Erin Catto’s powerful c++ physics library.

Papervision3d Daily is the blog where you come to see the latest news about PV3d, mostly we’ll focus on websites and demos. But we also aim to make the announcements for the community.

But if you have code related issues, or are just looking for good tutorials, not just on Papervision3d but on flash/flex in general go to Dreaming in Flash , Papervision3d Daily big brother.

A nice overview of ActionScript 3.0 over at Senocular

“With Flash CS3 comes support for ActionScript 3.0 - the newest, standards-based programming language for Adobe Flash (SWF) movies and applications. More so than in the past, you may find it difficult to get started with ActionScript 3.0 when compared to older versions of ActionScript. The transition to ActionScript 2 from ActionScript 1, for example, can probably be seen as a cakewalk compared to the leap to ActionScript 3.0, especially for someone who is prone to working and coding in the Flash IDE (Integrated Development Environment).

The goal of this article is to help acclimate you to working with ActionScript 3.0. It will focus on using ActionScript 3.0 within the Flash CS3 IDE, the first version of the Flash authoring environment to support this new version of ActionScript.”

http://www.senocular.com/flash/tutorials/as3withflashcs3/?page=1

http://www.insideria.com/2008/01/actionscript-30-is-it-hard-or.html

Colin Moock’s latest article for O’Reilly examines the difficulty of learning and using ActionScript 3.0, compared with ActionScript 2.0 and ActionScript 1.0.Executive summary: I argue that ActionScript 3.0 itself is not harder to learn or use than previous versions, but that there are some important issues in the Flash authoring tool that make ActionScript 3.0 less approachable for small-scale programs and inexperienced programmers. Specifically:1) on()/onClipEvent()-style events are gone2) parent.gotoAndPlay() requires a cast3) deactivating display assets that are no longer in use takes more workThe first two issues should be relatively easy to fix. The third might not be fixable at all. One other, more minor issue: you can’t dynamically change a symbol’s class at runtime (as previously possible via Object.registerClass()).