If you are using the Jmol.js JavaScript library then you *must* read this.
Jmol v10pre18/19 introduced changes to the way that Jmol.js needs to be
initialized.
jmolInitialize() is a new important function. It *must* be called before
anything else
jmolSetCodebase() has been (effectively) deprecated. It is called by
jmolInitialize() and (under normal circumstances) should not be called
directly.
jmolInitialize(codebaseDirectory, {unsupportedBrowserURL}, {noJavaURL})
codebaseDirectory is the directory where JmolApplet.jar is located. This
is a required parameter.
unsupportedBrowserURL and noJavaURL specify where the browser should be
redirected if the browser is not supported by Jmol (or if Java is not
installed/enabled). These are optional parameters. If they are not passed
then an alert box will be brought up to warn the user.
Your code should contain a call to jmolInitialize with the
codebaseDirectory as the first call. A simple page might say
[body]
[script]
jmolInitialize(".");
[/script]
A more complex sight might contain
[body]
...
[script]
jmolInitialize("../jmol",
"../error/badBrowser.html",
"../error/noJava.html");
In addition, Jmol.js now gently *reminds* you if you use
jmolButton/jmolCheckbox/jmolRadioGroup/jmolMenu without specifying
[form][/form] tags
Finally, when a user presses the reload/refresh button, the state of the
form controls (checkboxes, radio buttons, menus) is now reset to the
inital values.
Feedback is always appreciated.
Miguel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Jmol-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jmol-users
