User:Eric Martz/How JSmol works
From Proteopedia
(Difference between revisions)
(New page: This is a non-technical overview of how JSmol works in websites, such as Protopedia, FirstGlance in Jmol, and many others.) |
|||
| Line 1: | Line 1: | ||
| - | This is a non-technical overview of how JSmol | + | This is a non-technical overview of how JSmol and [[Jmol]]) work in websites, such as Protopedia, [[FirstGlance in Jmol]], and many others. |
| + | |||
| + | ==Providing JSmol== | ||
| + | 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). | ||
| + | |||
| + | In order to invoke JSmol, the files on the website server must also include | ||
Revision as of 20:56, 4 March 2017
This is a non-technical overview of how JSmol and Jmol) work in websites, such as Protopedia, FirstGlance in Jmol, and many others.
Providing JSmol
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).
In order to invoke JSmol, the files on the website server must also include
