We have 52 modules / libraries split roughly 1/3 to 2/3s, and a single main application.
Dozens of views, and dozens of custom components. Our biggest problem is dependency management between the libraries and modules. There is frequent refactoring of a module to pull code out into a library when its identified as being needed. Full build, including generating vos, compiling java code, compiling flex code, and deploying to the server is roughly 16 minutes. Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk <blocked::http://www.inps.co.uk/> The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [EMAIL PROTECTED] ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of tomeuchre Sent: 28 February 2008 23:03 To: [email protected] Subject: [flexcoders] Re: Best practices for setting up large applications? --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "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? > I am looking for something similar: I want to get an idea of what some of the largest Flex apps ever built (and utilized on a routine basis) are. I have one with 11 different views, and about 35 components, and it is about 1.5mb to load. Anybody have examples of larger ones? If so, what kind of issues do you run into?
