User:Eric Martz/How JSmol works: Difference between revisions
Eric Martz (talk | contribs) No edit summary |
Eric Martz (talk | contribs) |
||
| Line 6: | Line 6: | ||
A website has, at the very least, some hypertext markup language files (filenames ending .htm or .html). Usually there are also some image files (filenames ending .png, .jpg, .gif, etc.) for images that are displayed in the web pages. And usually there are also some [https://en.wikipedia.org/wiki/JavaScript JavaScript] files (filenames ending .js) and some cascading style sheet files (filenames ending .css). JavaScript (not to be confused with [[Java]]) is a programming language that is interpreted by the [https://en.wikipedia.org/wiki/Web_browser web browser]. | A website has, at the very least, some hypertext markup language files (filenames ending .htm or .html). Usually there are also some image files (filenames ending .png, .jpg, .gif, etc.) for images that are displayed in the web pages. And usually there are also some [https://en.wikipedia.org/wiki/JavaScript JavaScript] files (filenames ending .js) and some cascading style sheet files (filenames ending .css). JavaScript (not to be confused with [[Java]]) is a programming language that is interpreted by the [https://en.wikipedia.org/wiki/Web_browser web browser]. | ||
In order to invoke JSmol, the files on the website server must also include the javascript code for JSmol (filenames ending .js). If the Jmol Java applet is to be invoked, the Java archive files for Jmol (filenames ending .jar) must also be included. All these are included in the download package from [http://jmol.sourceforge.net/download/]. | In order to invoke JSmol, the files on the website server must also include the javascript code for JSmol (filenames ending .js). If the Jmol Java applet is to be invoked, the Java archive files for Jmol (filenames ending .jar) must also be included. All these are included in the download package from [http://jmol.sourceforge.net/download/ jmol.sourceforge.net/download]. | ||
Revision as of 01:28, 5 March 2017
This is intended to be a minimally technical overview of how JSmol and Jmol work in websites, such as Protopedia, FirstGlance in Jmol, and many others.
Providing JSmolProviding JSmol
The website server provides not only the web pages, but also JSmol. The web browser simply displays JSmol, and molecular data, provided by the server. Thus, the version of JSmol is matched to the web pages. JSmol is updated frequently at Jmol.Org, but the version of JSmol on a given website remains fixed until the site administrator upgrades it.
A website has, at the very least, some hypertext markup language files (filenames ending .htm or .html). Usually there are also some image files (filenames ending .png, .jpg, .gif, etc.) for images that are displayed in the web pages. And usually there are also some JavaScript files (filenames ending .js) and some cascading style sheet files (filenames ending .css). JavaScript (not to be confused with Java) is a programming language that is interpreted by the web browser.
In order to invoke JSmol, the files on the website server must also include the javascript code for JSmol (filenames ending .js). If the Jmol Java applet is to be invoked, the Java archive files for Jmol (filenames ending .jar) must also be included. All these are included in the download package from jmol.sourceforge.net/download.