Shawn, Bill's suggestion of puting a framework in place is completely valid and I believe you should. However, I think you should take some time (I know it is difficult when trying to get something done) and explore the various frameworks and how they are used completely.
Cairngorm is probably a good fit for what you are trying to do, but I am hesitant of puting a reference or variable to anything you need in the ModelLocator. IMO, it tends to dillute the efficacy of this pattern and can make code that is more tightly coupled than you started with, just in a different way. Best of luck and read up on your options. There are many good resources and opinions about frameworks online. -labriola P.S. I think I am going to start a new organization called "People for the Ethical Use of Cairngorm." --- In [email protected], "shawn.gibson" <[EMAIL PROTECTED]> wrote: > > >In this case, it looks to me like you are following references down > through from the loaded module which, even if you find the right > path, is going to come back to haunt you if you ever make a change to > that nesting. > > The entire point to me, is that I have what is invariably going to be > a pretty complex application, and I need to ensure there are as few > dependencies as possible. I suspect there will be maybe 100 or even > more unique files (app, modules, components, .as files, xml > files...not to mention a few dozen db tables), just for code, > excluding images etc...so having as many of those little files as > non-dependent as possible is definitely the ideal for me. > > I've learned enough that I know Application.application.etc is a BAD > thing for my requirements... > > Shawn >
