Consider that many js files making the JSmol library are not called directly by the webpage, but by other js files. If you change the version of JSmol library that is used by the page, it may prove harder to make the browser disregard the old files in cache. But this will often solve just case #1, maybe #2. Caching the model files (pdb, mol.) and script files that are loaded into JSmol by code in the page.Ĭlearing the browser cache is easy, although sometimes it takes several tries or closing and restarting the browser.js files -including the JSmol library files. There are several levels of file caching in a typical web page with JSmol object. It is a warning for the page developer, who may disallow it in the page code using Jmol._alertNoBinary = false Cached files However, the success may depend on the browser being used. This is harmless you may disregard it as long as the page works (models are loaded). Synchronous binary file transfer is requested but not available Problems running the JSmol/HTML5 (non-Java) modality of the Jmol Object in a web page Synchronous binary file transferĪn alert may be displayed on some pages, depending on the browser you use, saying 3.1 Copying code from the script console.3 Extracting information from the Jmol applet.2.4.2 Jmol does not respond to controls in page (Mac Safari).2.4.1 Popup menu does not open and server errors (Fedora).2.3 Jmol and model are displayed, but further actions have no effect.2.2 Jmol is displayed, but models are not.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |