In depth discussion

Question

So, I have been attempting to modify
David
Stillers "Loading and Tracking Multiple Files at the Same
Time". In his approach you add the items you want to load to an
array and then make a call to load them. The issue that I have is
when loading an external swf files it will fire off an
onLoadComplete because the swfs file size has been loaded, this is
not an accurate assumption as the external swf that is loading
maybe loading in additional files, jpg, sound, video etc. So, I
have been trying to grasp and outline how best to approach the true
loading of all content for an application when loading in external
swf files and have come up with the following.
// Load handling.
Requires that each swf has a var boolean to show itself as
either loaded or not loaded.
Use a private variable so nothing but the swf can set it.
Use a getter method to so parent swf can obtain the value.
This flag may only get set when to true when.
1. The swf has no children and has inited i.e. set the var
using onEnterFrame
2. The swf loads external files other than swf such as txt
jpg mp3 etc. that do not load other files and all files have loaded
3. The swf loads external swfs (This is a recursive ideology
as swfs can load other files and or other swfs and the cycle in
theory is infinite but in practice it is not as no application is
infinite) which resolve against these conditions 1,2 and 3
So, the loading process is by logic always Parent -->
Child
The setting of the var for the load status of each swf
process is Child --> Parent
Meaning no swf can be deamed loaded if the child swf is not
loaded. So a child must be flagged as loaded in order for a parent
to say that itself is loaded.
Now, I am a firm believer that NO CHILD should ever be
calling a parent swf because each swf is a self contained object.
So by the Child --> Parent reference above this is how I
mean.
When a parent is loading in an external swf and the
onLoadInit / or onLoadComplete (undecided on which to use so far)
triggers saying that the swf has loaded, the code shall use a
setInterval, thus creating a looping call to the child swfs asking
if they are loaded. This method will continue to call until the
true status of the child is set. Once all the content has been
loaded for a call then proceed as your project requires.
By basing the approach from David Stillers code one can
create different loader sets such as 1 loader to load in all core
application components, 2 load in configuration files, 3 loading in
additional optional components and 4 loading in data
// Error handling
Requires that each swf has a var array:String to capture any
errors so they can be displayed if running solo or pulled from a
parent.
Use a private variable so nothing but the swf can set it.
Use a getter method to so parent swf can obtain the value.
Now in the event that a child has an error, we need to be
able to handle issues where a child is deemed never loaded due to
an error that may arise i.e. missing jpg file. This is where i have
left off as my focus has been on the above idea. The error handling
can be discussed later but for now I just wanted to inform those
who are interested in this topic that I am aware of it.

Answer 1

If I was using a loaded swf to load additional content and
wanted its parent to be notified, I be more inclined to have code
on its timeline which initializes it with EventDispatcher to have
it dispatch custom events. Or (probably) have a dedicated loading
class that it uses which dispatches events. And then set up
listeners in the parent for its custom events in the onLoadInit
handler once it has loaded. I think this would be the better way to
go to avoid the time-based loop checking of a ready state in the
loaded swf. My 2 cents worth.