Executing an Air application has a non negligible runtime cost. I did a few tests to see how much memory and CPU a very simple Air Ajax application uses.

Added some more Papervision 3D examples with source code.
All examples use current Papervision3D GreatWhite from SVN and so far all use BasicView also.

Following from my last post, I'd like to show how Papervision3D v2.0 provides us with a class to encapsulate the viewport, camera, scene and renderer. This class is called the BasicView and is basically a wrapper class for all these objects. Rather than inheriting from a Sprite, this example is derived from the BasicView and as a result inherits automatically the four key objects named above.

In this post I hope to show how, in a few simple steps, we can create a simple 3D scene in Actionscript 3 using Papervision3D. As I've mentioned in previous posts, I'm no expert and am merely posting on the web the experiences I've had over the last few weeks in starting myself. A couple of useful links providing an introduction to 3D techniques and Papervision3D features provide a good starting point.

James Ward politely pointed out some links where I could see more Flex in action (not the book). After spending some time doing this I started doing a bit of home brewing of my own with Flex. Here are a few reasons why Flex looks appealing to me (in no particular order).

The default Hallo skin doesn't allow background-position-ing

Looping over the data used by a Flex List component is easy enough, but what if you need to loop over the actual itemRenderers in the List? Recently I needed to do just that.

This tip will help you create an easy to use, re-usable class that will set up an external XML feed to use E4X, datagrids, etc.

This blog-post examines ActionScript and JavaScript in the perspective of Object Oriented programming. The article starts with showing how these languages derive some basic concepts from Smalltalk (well, actually Self), and perhaps Scheme, while keeping Java-like syntax, goes through comparisons and observation about the languages and their platforms and in the end discusses the future of web programming.

BlazeDS will not scale very well, because the HTTP requests will never be cached.