Using Modules is the one way to reduce the size of swf's from one to many. But, it's a big hassle while you are developing your application. As every build time is more as other modules are also part of your application and if many dev working on different modules, then dependency increases on others.
What we tried here.. instead of Modules, we divided our big application into many small application and put an umbrella application on top of all. The benefits we got out of it, is modularization, lesser build time, lesser overhead and lot more.. We are using Flex 2. Definitely there will be some advantage with Flex 3. But on top of all that, dividing a big application into many small one's gives us a lot of comfort. (Earlier we were using the modules and it was pretty tough to deal with that ). Thanks, Manu. Guy Morton wrote: > > Another question > > We have an app that has a number of parts that are not all required > for all customers. What's the best way to build it to minimise file > size and for ease of building and code maintenance? > > We currently keep the code separated in different classes and mxml > components, so we can do things like comment out things we don't want > to reduce the size of an individual build but I'm figuring there must > be a better way. > > Currently we are building in FB2, but are about to upgrade to FB3, if > that makes a difference. > > Guy > > -- View this message in context: http://www.nabble.com/Modularising-a-flex-app-tp19467861p19472476.html Sent from the FlexCoders mailing list archive at Nabble.com.
