That has taken a fair bit of Googling to figure that one out. Because of security sandbox restrictions, when using the url of the ModuleLoader component, modules can only be loaded from the application directory (or any of its subdirectories).

Solution adapted from Enable Local App to load RunTime CSS.swf from Server

That has taken a fair bit of Googling to figure that one out. Because of security sandbox restrictions, when using the url of the ModuleLoader component, modules can only be loaded from the application directory (or any of its subdirectories).

Solution adapted from Enable Local App to load RunTime CSS.swf from Server

{syntaxhighlighter brush: as3}
private function loadModule():void
{
var file:File = File.userDirectory.resolvePath("test/MyModule.swf");

When I started experimenting with the mx:HTML tag in AIR, I ran into a series of problem. Javascrpt code that would run perfectly fine in the webkit browser running on the desktop would not run correctly in an AIR app (using the same version of webkit) .

This article is part of group of posts on Flex project setup or five use cases for multiple source paths linking.

• Part I. A better way to set up flex unit
• Part II. Using a subproject for ui experimentation and development of helpers for the team
• Part III. The advantages of keeping Data Providers in their own source path
  

This article is part of group of posts on Flex project setup or five use cases for multiple source paths linking.

• Part I. A better way to set up flex unit
• Part II. Using a subproject for ui experimentation and development of helpers for the team
• Part III. The advantages of keeping Data Providers in their own source path
• Part IV. Mock Data as an alternative Data Provider
  

This article is part of group of posts on Flex project setup or five use cases for multiple source paths linking.

• Part I. A better way to set up flex unit
• Part II. Using a subproject for ui experimentation and development of helpers for the team
• Part III. The advantages of keeping Data Providers in their own source path
• Part IV. Mock Data as an alternative Data Provider

This article is part of group of posts on Flex project setup or five use cases for multiple source paths linking.

• Part I. A better way to set up flex unit
• Part II. Using a subproject for ui experimentation and development of helpers for the team
• Part III. The advantages of keeping Data Providers in their own source path
• Part IV. Mock Data as an alternative Data Provider

This article is part of group of posts on Flex project setup or five use cases for multiple source paths linking.

• Part I. A better way to set up flex unit
• Part II. Using a subproject for ui experimentation and development of helpers for the team
• Part III. The advantages of keeping Data Providers in their own source path

I had a chance to give a talk at the Wellington User Group recently. In the process of preparing it, I discovered a few new tricks and solidified a few old ones.

What I will describe here is how you can take advantage of source import to set up your flex project to enable parallel development of an official release, unit test, web service test, ui development and experimentation, mock data.

At its worst, you will end up with a reserved workspace in Flash Builder that contains the following projects:

First attempt at creating a mini-game with Flex on the nexus one.

Determine the direction of the fish by moving your device up and down and left and right.

The video was taken using some box contraption that ensures that the camera moves in parallel to the device, to ensure that the screen remains in focus. Any up and down or left and right movement appears weaker than it actually is.

source: Mobile revolution by Serge Jespers

Gestures

public function init():void 
{
   Multitouch.inputMode = MultitouchInputMode.GESTURE;
   logo.addEventListener(TransformGestureEvent.GESTURE_ROTATE, onRotate );    
   logo.addEventListener(TransformGestureEvent.GESTURE_ZOOM, onZoom );
} 

priv

source: Mobile revolution by Serge Jespers

Gestures

{syntaxhighlighter brush: as3}
public function init():void
{
Multitouch.inputMode = MultitouchInputMode.GESTURE;
logo.addEventListener(TransformGestureEvent.GESTURE_ROTATE, onRotate );
logo.addEventListener(TransformGestureEvent.GESTURE_ZOOM, onZoom );
}

private function onRotate(evt:TransformGestureEvent):void
{
// pssst... you should try rotationX or Y
logo.rotation += evt.rotation;
}