What I was trying to get at is that the last step where you flip the top tag from mx:Application to mx:Module would be skipped. It would remain an application. In the loading app, you would not use ModuleLoader and use SWFLoader instead. There is no restriction on the sub-app being in the same project as the main app, but if you choose to do so, you are correct that it should be a one-time thing. The scary part will be the way you will have to code communications between the sub-app and the main app for anything shared like data, networking, managers, etc. We're still working out the details.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Nate Pearson Sent: Monday, May 12, 2008 3:00 PM To: [email protected] Subject: [flexcoders] Re: Working with modules Thanks for the response guys. So it sounds like in a future version of flex I might have to move all my modules into one application and make them sub apps, but I would only have to do that once, right? That doesn't sound that scary :) *crosses fingers* --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > Yes, or build a shell app that loads the module. > > > > BTW, while modules are smaller and faster than sub-applications, they > are also more tightly bound as the must use interfaces to communicate > with the loading application.. This means that, over time, as your > application grows, if your app is comprised of modules, you'll probably > need to recompile all of them if you move the main app to a later > version of Flex. > > > > The same may not be true of sub-applications. While they are fatter, it > may be possible in a future release of Flex to make it so they have no > tight coupling to the loading application and thus, if your app is > comprised of sub-applications, you won't necessarily have to recompile > every sub-app. > > > > Of course, none of that truly matters now as in order to break > tight-coupling we'll probably require that you re-compile all of your > pieces as sub-applications on that future version of Flex so you are > protected as you go forward. It is unlikely that anything you compile > in the interim will work with future versions of Flex. But I wanted to > warn you and anybody else who cares that the future of handling > applications where it is impractical to recompile everything onto a > single version of Flex is probably going to involve sub-applications and > not modules. > > > > -Alex > > > > ________________________________ > > From: [email protected] <mailto:flexcoders%40yahoogroups.com> [mailto:[email protected] <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of Nate Pearson > Sent: Monday, May 12, 2008 2:18 PM > To: [email protected] <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Working with modules > > > > I'm building an application with multiple modules. Each module is a > different project in flex builder. I have a main application project > that each module compiles a swf to. > > I want to be able to run each module by it's self to develop/debug it. > I can't figure out how to do this. > > My module projects start out as <mx:application> but when I change it > to <mx:module> I can't run it and get any output (even though it has > that green arrow). > > Maybe I just answered my own question, should I just leave it as > <mx:application> until I'm done developing then switch it to a module? > > Thanks so much for the help, > > Nate >
