I took the example from the html tutorial:

A user agent must interpret an OBJECT element according to the
following precedence rules:

   1. The user agent must first try to render the object. It should not
render the element's contents, but it must examine them in case the
element contains any direct children that are PARAM elements (see
object initialization) or MAP elements (see client-side image maps).
   2. If the user agent is not able to render the object for whatever
reason (configured not to, lack of resources, wrong architecture,
etc.), it must try to render its contents.

Authors should not include content in OBJECT elements that appear in
the HEAD element.

In the following example, we insert an analog clock applet in a
document via the OBJECT element. The applet, written in the Python
language, requires no additional data or run-time values. The classid
attribute specifies the location of the applet:


<P><OBJECT classid="http://www.miamachina.it/analogclock.py";>
</OBJECT>

Note that the clock will be rendered as soon as the user agent
interprets this OBJECT declaration. It is possible to delay rendering
of an object by first declaring the object (described below).

Authors should complete this declaration by including alternate text as
the contents of OBJECT in case the user agent cannot render the clock.


<P><OBJECT classid="http://www.miamachina.it/analogclock.py";>
An animated clock.
</OBJECT>

One significant consequence of the OBJECT element's design is that it
offers a mechanism for specifying alternate object renderings; each
embedded OBJECT declaration may specify alternate content types. If a
user agent cannot render the outermost OBJECT, it tries to render the
contents, which may be another OBJECT element, etc.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to