We had the same problem in AS2, where we basically build the whole Flex engine in AS2 / XML, plus everything else the application needed to do, more than 50k lines of code. Flash 7 was compiling it for 3 minutes. We couldn't move or change anything without destroying things somewhere else. We also thought that's the best way compared to what other teams were doing, we were really proud of it in the beginning :)
It basically depends how you structure classes, libraries, so they can be used independently in different projects. Less inheritance, more composition, domain objects, decorator objects, Cairngorm also helps, and above all experience. I don't know, it depends on project to project, I doubt there is one single recipe you could follow to have everything in order. Alen --- In [email protected], "Geoffrey" <[EMAIL PROTECTED]> wrote: > > We currently have a master project that links in 25 other projects to > build our overall application. The problem with this is that there > seems to be a lot of inner dependencies b/w the projects (i.e. one > project is a collection of utilities, and several other projects use > these utilities). Builds also seem to take forever when you change a > project that is linked to many other projects. > > We initially thought that this would be a good way to set up our > application so we could take out certain parts to customize our > offerings to customers. Just not sure that it's really giving the > advantages we initially thought. > > Any thought on this? >
