Exploring companion planting with a particle system. Peppers like Peppers. Carrots like Onions. Potatoes don't like anything... and dislike other root vegetables like carrots.

source view

My husband bought a Kinect and released an application that let you run kinect from your USB port, without having to install any driver. Check out cocoakinect project.

Anyway, I noticed that a actionscript wrapper was provided in the openkinect/libfreenect libraries on github. With a helping hand from my husband, got the as3server running. Once it is running, rgb and heatmap pictures can be viewed by running mxmlc test_depth.as or test_rgb.as (provided in the libfreenect library). If you have Flex installed, simply run 'mxmlc test_depth.as' from the command line.

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

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: