Every GC issue that applies to modules also applies to sub-apps. You should use sub-apps if you can’t gurantee that all modules will be compiled on the same SDK.
On 5/6/10 3:58 PM, "Hilary Bridel" <[email protected]> wrote: HI Jeff, I am not surprised that there are no replies to your post. I have been researching this question for a project just about to start, and I cant find much information. I am struggling with the decision about if/should we go with modules or sub-applications, because there are so many issues with GC and unloading modules. I would be interested to learn which way you went with this. Regards Hilary -- On Fri, Apr 2, 2010 at 2:10 AM, Jeff <[email protected]> wrote: We are building an application to create many types of diagrams. The intent is to have a main application that acts as a general loader for many diagram types implemented as modules. The dilemma is whether to break the modules out into separate flex projects or to include them as subdirectories of the main application's project. I've seen some of the adobe documentation but I'm hoping that someone has some experience/insights as to which is the better approach. Thanks. -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
