Does anyone know of a resource that specifies the best way to structure a very large Flex project? Our current Flex 3 project is comprised of 30 separate flex projects that each represent a 'display' within the overall application.
So there's the main app project which is pretty small. It has the main application mxml, and support files that go with it(pngs, css, mxml/as that is specific to the main page of the app). Then there are about 13 other projects that are the displays linked off the main page. The rest of the projects are support or common code that is used across the application. For example, we have a Value Object package to keep all the VOs in one place. The problem we're having is that building Flex projects crashes Eclipse with out of memory errors. We're trying FB4, but that doesn't seem to be helping. Oh yea, using SDK3.3.0. Each project can be quite large, so I'm assuming that it's crashing when loading the classes into memory. I guess what I'm looking for is a best-practice architecture resource for laying out very large Flex projects. Thanks, Geoff
