Thanks, that information is helpful. However, I'm trying to avoid running a local server, since the back-end is .NET and I'm on a Mac.
I guess I could copy the modules to the loading app's output directory, and maybe set up an Eclipse builder to do this transparently. Or perhaps I could point the output folder for the loader and all modules to the same place. On Fri, Apr 11, 2008 at 12:29 PM, bobpardoe1959 <[EMAIL PROTECTED]> wrote: > > > > > > > We create all of our module projects under a modules directory, each > one having their own sub directory. Each project has its own bin-debug > directory created by FB. We then use an ant script in FB to iterate > through all of the module\**\debug-bin directories and copy the swfs > to the dev's local jboss deployment directory from where we then run > the app. > > We point the FB debug scripts to the dev's local jboss url and run it > all from there. > > We have to create deployment scripts for the live servers to build the > release versions and deploy them in the same way, but these are > centrally managed to make sure we always deploy the whole app and its > corresponding modules and libs. > > In either JBoss instance we put all of the modules into a single > directory that sits parallel to the app's directory and load it all > from there. > > HTH > > > BOb > > --- In [email protected], "Richard Rodseth" <[EMAIL PROTECTED]> > wrote: > > > > Thanks Bob. In dev mode (Flexbuilder only) is there a convenient way > > to reference the module SWFs by a relative URL, or does one have to > > copy them into the loader app's output directory? > > > > On Fri, Apr 11, 2008 at 7:42 AM, bobpardoe1959 > > > <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > > > > > > > We do exactly this. Each module is a project. This allows each > > > developer to create \ compile \ run a project without reference to > > > another dev. We load each module in the app (at runtime) on demand > > > using the moduleLoader. (Watch for the intermittent loader bug and > > > knock on popup bug !) > > > > > > The down side to this is that we cannot find a way to compile quickly > > > as each project seems to load the jvm for a compile. This is perhaps > > > more apparent in a release build where the compile is done by Ant > on a > > > module by module basis rather than the incremental build in Eclipse. > > > It is how ever dog slow when you do a full clean and rebuild. > > > > > > The other issue that we havent yet rectified, is that each dev can > > > have 1..n number of modules and they wont all be the same as we dont > > > manage each dev's workspace through a source code repository. > > > > > > Oh yes, by the time our project is finished we expect to have about > > > 180 or so modules. > > > > > > Hope this helps > > > > > > BOb > > > > > > > > > > > > --- In [email protected], "Richard Rodseth" <rrodseth@> > 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? > > > > > > > > > > > > > >
