I don’t yet have tested to load Flex 4 modules with this demo. The only thing I know is that removing module is crappy in Flex 3, even with this demo, the garbage collector passes randomly. Something special probably happens with Flex 4 modules. I’m interested in any new informations, let me know.

I first created an actionscript project Main in a new project workspace. then I create a Flash file in Flash CS5 Shell.fla and saved it under my project folder and then created the document class for the Shell.as inside my com.project.shell.view.components folder and this created a new Flash Pro Project in Flash Builder.
I changed the output folder in project settings to point to Main project bin-debug. Shell.gets compiled there and then I added a libs folder for my swc’s.

Thing is my Shell.swc gets put in the same folder as Shell.as. along with another Shell.swf and I,m not sure if debugging is set for Flash builder . any suggestions ? thanks again

the real document class for the demo is here the PureMVC_FlashModulesAndPipes class. The Shell class is only the view component that instantiate the Shell “module”. The HelloModule follow the same convention. Its base view component class is located in the “view.components” package.

But you can do as you want to. Here the modules were compiled from the same application as I want the application to be compiled from Flex Builder. But in real life you will often have a different application folder for each module. So if you prefer to, in this case just put the document class in the default package, I don’t think this matters.

Now, I will wait for the CS5 suite to be there (only a week left). As Flash CS5 can now supports .SWC files, I will try to rewrite this demo to be Flash only to get rid of the Flex Builder structure it has. I only hope to be able to generate the “Browse Source Meu” from Flash CS5.

I’ve returned to look over your code for this demo as I embark on another pureMVC Actionscript 3 project (Flash only)…

My question to you is about application architecture:

In the source for your project posted here, you have the Shell.as Class located in the shell.view.components package. I’m finding this confusing: I thought that in a Multicore application, the Shell was synonymous with the Document Class, is it not? Why wouldn’t the Shell exist at the top level of the application? Is it not technically the daddy of all Document Classes?

Thanks, sd