I am going to begin to build a website entirely in expensive (per the client's request), using AS3, and wondered about guidelines for doing this when it comes to application architecture. The website is not too big--think home page, persistent nav, 8 subsections approximately, each using their own content but similar design between subsections. Previously, I'd used multiple swfs (say, one for that nav and something each for that subsections) and loaded them dynamically now, though, I am thinking about going for a different route and taking advantage of a far more object-oriented design, with a lot of classes and merely one swf (along with a preloader to load it).

What are the best-practices for identifying be it easier to dynamically load more compact swfs versus creating a single large swf? In AS2 I believe loading many more compact swfs made more sense, however with AS3's more powerful object-oriented abilities I am wondering if that is still the situation.

I understand that certain argument from the single-swf design will be the added weight of loading everything upon initial siteload, however i don't believe there's enough heavy content it's of real concern here.

Any ideas?

It is dependent on which you mean by "more compact."

Don't break it into portions which are not big enough or you'll kill yourself with connection overhead. Don't pack the entire site into one mammoth pile which will takes days to download.

A great guideline: when you are attempting to come up with appealing or entertaining items to display while your customers are waiting for this to download, restructure rather.

-- MarkusQ

I thinks this heavy is dependent around the content from the pages and just how many assets you have incorporated in your soul swf.

We usually simply make 2 swfs: one preloader and also the real application.

The programs doesn't have any text or images incorporated. Everything (except fonts) loaded dynamicly in the server because the submissions are dynamic of all in our cases. How big the swf doesn't increase much you add another 10 classes.

The it's difficult to provide a 100% direct response to you question, as stated it is dependent around the weight from the content (and whether it's dynamic or very static).

In my opinion, the most popular practice nowadays for (most) promising small to medium Expensive websites/programs is really a two SWF architecture, a spend that loads a core. Sometimes you are able to manage with only one SWF that tracks its very own load progress. Nevertheless, you need to load content and assets when needed images, video, animations and enormous text message. These typically shouldn't be baked into the core SWF but loaded on user request. The main advantage either in situation here (one versus two SWFs) is code maintenance. You simply need recompile the core SWF whenever you make updates towards the application. Within this model, you can still load additional SWFs that contained timeline-based animations, as lengthy while you stored the application code within the core.

Hope that can help!