What next?
If you're trying to understand how this work, continue reading.
If you're trying to modify this application to match your needs, go to the
last page, where we explain some essentials about changing layout. For further
customization, just ask in Boards
Building plan
Here's the plan for the application ... well, really the final one. Previous drafts were omitted in sake of simplicity
As you can see, this is ambitious and sounds complex ... and it was. The complexity isn't around the code itself, but in the relationship between classes. Also not always the requirements of the pattern match your needs, and sometimes even it complicates things. But if you begin to allow exceptions, then things doesn't work as expected, specially when trying to modify your initial sketch.
Files
There are only three flash files: gallery.fla, videogallery.fla and bigGallery.fla. The first implements all variations listed, the second is specifically for the video example, while the third implements a couple of variations in a big format. All what you need to do is to coment/uncoment proper include based on your needs. All the folder structure cover the need of separate each combination of classes. The main folder have the basic triads, the mvc have the basic implementations for Model and View, the util folder have the basis for the Observer and Iterator. When uploading to the server, you only need the swf, photos or video folder and PHP stuff if you use the database model. That's because classes are compiled into the swf, not loaded at runtime.

5 most recent
Flash streaming servers
Tree menu
Flash Spell Checker
Flash Remoting Library
MX 2004 Chart/Poll
Applications