A common approach is to create a library project for common components (you'll need to add source paths). That way you only have to make changes in one place. Also, if an application or module doesn't use a component, it will not be compiled into the swf; so you don't have to worry about increasing the file size.
-TH --- In flexcoders@yahoogroups.com, "rockorgames" <eguilhe...@...> wrote: > > i have a simple question.. i have several modules and some mxml > components, where those components are used in several modules, but > arent used at all in the main application.. > > now should i remove those components from the main app (since if the > user never load the module that uses them, it will be just wasting > space in the main swf) and add their code manually to only the modules > that uses them (but if i change the code in 1 place i ll probably need > to change it in all the others as well.. ) ? > > or should i make my components become modules aswell ? (the problem > with that is that those components arent opcional for the modules, so > making the user load 2 swfs instead of only 1 is quite wrong i think) > > or is it possible to make the component only increase the modules > size? but not the main app (since it doesnt use them) > > so what do you guys think ? > > for eg: > > i have a zip search component.. but only a few modules uses it.. > should i copy the code from the zip component to those modules ? the > problem is that i would have to change the code in all modules if i > needed to change something in the zip process >
