Jaime was mistaken. JavaScript communications with the JmolApplet does not work on MacOSX with Java 1.4.2 ... regardless of whether or not you use Jmol.js
Note that I do not yet have a Mac, so I cannot test this. Nevertheless, I am quite confident that I can explain the behavior. Jaime wrote: > As you may know, the latest Java update in Mac OS X brought Jmol > to a catastrophic situation: the Safari browser dies instantly. > > Solution: use plain JavaScript, not Jmol.js, until there's a > new release either from Apple or Jmol.js We seem to have a little confusion over browser scripting terminology/technology. I will explain ... > I've just found that Jmol 10pre13 works fine with the problematic > Java 1.4.2 update on Mac OS X as long as you avoid Jmol.js > > Maybe the whole problem resides in the way Jmol.js finds and > manages applets in the page. > > Take a look to http://bip.weizmann.ac.il/oca-docs/jmoltest/jmol2.html Your demo page shows two applets. The applet on the left does *not* use Jmol.js ... and it works The applet on the right *does* use Jmol.js ... and it dies. However, the applet on the left is not using JavaScript either. The buttons are running the script by using the JmolAppletControl. This is the applet-to-applet communications mechanism that works without using JavaScript or LiveConnect. So, that is why it is working. The problem is using LiveConnect and is not specific to Jmol.js Any JavaScript calls that try to invoke applet methods will die ... independent of whether or not they are made through Jmol.js Miguel Miguel ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Jmol-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-users
