marc wrote:
From the book I am using as a reference I understood that applet tag
was deprecated, but googling for information, and testing myself, it
seems IE does not work properly with this new object tag. So my effort
reading about the object tag was for nothing? Is there no way I can
make this work for IE and Mozilla?
Leaving out that Java applets (not applications!) is mainly dead
technologie:
<object> for Java is *very bad* because it implies a particular JVM to
use. In the mixed environment (IE / others) it often happens that IE
uses much more effective Microsoft JVM and "others" have to function
under Sun plugin. More over "others" may have Sun plugin of one version
and your <object> will imply another version. Sun did so many plugin
variants and patches that they have lost the count themselves. It
caused in the past several major virus-like epidemies across
Java-users: you have plugin 1.3.0, applet object codebase implies
1.3.1, it downloads 1.3.1, breaks your 1.3.0 plus make it default VM
for Microsoft which already had MS JVM...etc...
All together is the best way to make the whole system dizzy. Sometimes
you have to reinstall the entire Java segment on your computer after
viewing <object>-enforced Java applet. The above statement is a blood
written one, trust me.
To somehow fix this "Java-virus" Sun introduced classid
8AD9C840-044E-11D1-B3E9-00805F499D93 which internally supposes to mean
"the latest JVM you installed on this machine". Still it doesn't help
to prevent IE with Microsoft JVM installed from failure because
Microsoft JVM classid is 08B0E5C0-4FCB-11CF-AAA5-00401C608500
<applet> tag means "use any JVM you have - if you have any". Despite it
is deprecated but at least it's secure against of occasional system
damages.
If you still want to have applets on your page, use the old
Microsoft-proposed workaround:
<applet class="myClass. class"
cabbase="myAppl et.cab"
archive="myAppl et.jar"
....
After meeting "cabbase" MS JVM will ignore "archive".
Sun JVM will ignore "cabbase" and use archive.
It means that you'll have to have two archives (.jar and .cab)
Also Microsoft discontinued to support Java (but one can still find and
install the last version of MS JVM)
And indeed all this question is nothing to do with JavaScript or
JScript.