Mark Angeletti |
16 June 2006
This is a good time to
revisit our navigation XML file.
In order to retrieve values from an XML
file, we step through the family tree until you find the
desired value. So in our code,
xnRootNode.firstChild.childNodes.length;, the first child,
is <nav> and it has 4 child nodes -- you guessed it, they're
our 4 <button> nodes. So nTotalButtons is now equal to 4.
Next we use a 'for loop' to gather all the data from each of
our buttons and add it to our arrays.
astrImages is our array for images; the push method adds our
XML value to this array.
This may look scary at first, but let's
break it down.
xnRootNode.firstChild is <nav> its first
child is the first occurrence of <button> and <button>'s
first child is <image>. So far, so good, but what is
<image>'s first child? If you said, "button1.png" then pat
yourself on the back: that's correct. Even the text value
within the node is considered a child node in Flash. Lastly,
we use the nodeValue property to retrieve the node value of
the XML object, in this case "button1.png." Have a look at
the following table, as it may help:
We continue to fill in all our arrays, then
move on. Only after our XML data has completed loading and
has been pushed into our arrays are we ready to move the
playhead onward. Now, we move to our next frame.
Frame 3 is used to load our CSS file. Have a look at our
It looks like any other CSS file. We use CSS
to set the formatting on our buttons, which just keeps with
our paradigm of keeping everything external and dynamic.
Now that our CSS has loaded successfully, let's move on to