Accessing J(S)mol-containing webpages in local disk, or loading models from local files
When trying to load a page, some of these error warnings are shown in an alert box:
Symptom: trying to load an html file with JSmol/Java in Safari. The applet tries to load but then fails.
Solution: Safari > Preferences > Advanced > check the
Show Develop menu in menu bar option.
In the resulting Develop toolbar drop-down, check the
Disable Local File Restrictions option.
Caveat: when models in binary-format files are to be loaded, Safari may fail in any case for local files.
A command entered in the terminal allows to start up MacOS Chrome so that JSmol runs from local files:
open /Applications/Google\ Chrome.app --args --allow-file-access-from-files
(Make sure an instance of Chrome is not active when you issue that command.)
There is possibly a way to write an AppleScript to do this in one fell swoop.
You will be able to read both binary and text files locally. Please enter
about:config in the url address slot and then try setting as
false one of these:
If you need to open local files, first close all instances of Chrome and then try starting Chrome (from a command line or a shortcut) with one of these options:
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --allow-file-access-from-files
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-web-security --user-data-dir="C:\Users\my-user-name\Documents"
...or specifying as
user-data-dir wherever you have your html, JSmol and molecular files in your local disk.
It is not possible to load local binary files into JSmol/HTML5 from standard script commands. That is, no direct file reading with any of the following in their names:
.bin .gz .jmol .jpg .map .mrc .omap .png .pse .smol .spartan .zip
This does not apply to files drag-dropped onto the Jmol object or files loaded using "?", which use the HTML5 FileReader object. That method reads binary files without a problem.
Note: nowadays, you should avoid using MSIE for pages with JSmol. Its performance is much poorer and compatibility with some features is limited.
The same limitations apply regarding local binary files as those explained above for Chrome.