Separate projects is my preference and seems logical to me but is not really endorsed/recommended by Adobe which is disappointing. The compiler arguments you mentioned can be used to optimize but FlexBuilder is flaky at best using that approach. See https://bugs.adobe.com/jira/browse/FB-12220 for example. That thread also talks a bit about their recommended approach which, again, I am not crazy about.
HTH, Ben --- In [email protected], "Richard Rodseth" <[EMAIL PROTECTED]> wrote: > > I can't seem to find much about the pros and cons of having a separate > FlexBuilder project for each module in a modular, extensible app. It > seems you lose the Optimize For Application menu option, but can work > around that with compiler arguments. Besides, I don't think that's > appropriate in my case. > > Any opinions on best practices? >
