<DIV CLASS="soccer" x="200" y="250" onFifthBlink = "alert('Fifth Blink Point')"><IMG SRC="soccer.gif"></DIV> 

Now, let's add five more soccer balls, in different window's locations. The DIV line stays the same, except that the x and y attributes on each DIV are assigned different values:

<DIV CLASS="soccer" x="50" y="100" onFifthBlink = "alert('Fifth Blink Point')"><IMG SRC="soccer.gif"></DIV>
<DIV CLASS="soccer" x="100" y="150" onFifthBlink = "alert('Fifth Blink Point')"><IMG SRC="soccer.gif"></DIV>
<DIV CLASS="soccer" x="150" y="200" onFifthBlink = "alert('Fifth Blink Point')"><IMG SRC="soccer.gif"></DIV>
<DIV CLASS="soccer" x="200" y="250" onFifthBlink = "alert('Fifth Blink Point')"><IMG SRC="soccer.gif"></DIV>
<DIV CLASS="soccer" x="250" y="300" onFifthBlink = "alert('Fifth Blink Point')"><IMG SRC="soccer.gif"></DIV>

Sharing a single module by several elements is one of the cornerstones of any object-oriented languages. It is more than calling a procedure with different arguments. Object-oriented modules encapsulate both data and methods that can operate on this data. Behaviors are exactly that.

People who read this tip also read these tips:

• The IBuySpy Cornerstone Technologies
• The WSDL's message Element
• XML Namespaces
• Checking if Active Along the Timeline
• Using Attribute Values to Search for DOMDocument Nodes