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

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: