Jmol developers,
I'm drafting a summary of the file changes for Jmol-users. This is to
Jmol-developers first. Comments?
--------------------------------------------------------------
We were all a bit confused with the new file naming, so we've decided to
rename the applet files again -- just to thoroughly confuse you.
Actually, this is much better.
There are four distinct options that you can use when using the Jmol
applet. The typical user would only use one of these; we recommend the
first.
JmolApplet0*.jar
JmolApplet.jar
JmolAppletSigned.jar
JmolAppletSigned0*.jar
While we release all files associated with all of these options, you
only need the files associated with one of them. Most people will use
the first of these options.
Executive Summary
--------------------
If you are a typical Jmol user, just transfer the JmolApplet0*.jar files
to your server and include the simple form of jmolInitialize on your page:
jmolInitialize("directory-containing-jar-files")
JmolApplet0*.jar
------------------
A set of 16 files (currently) that together comprise all of Jmol but
arranged so that if your page does not require a component, that
component is not downloaded from the server. If you never use molecular
orbitals, that part won't be downloaded; if you only use PDB or CIF
files, only the PDB and CIF file readers will be downloaded. (They are
together in one of the files.) We still recommend putting all 16
JmolApplet0*.jar files on your server even if your page does not use the
capabilities provided by some of the files, because the pop-up menu and
Jmol console both allow users to access parts of Jmol you might not have
considered.
To use JmolApplet0*.jar use the simplest form of jmolInitialize(), just
indicating the directory containing the set of jar files:
jmolInitialize("../jmol")
JmolApplet.jar
---------------
A single jar file containing all Jmol applet components. Use this if
you want to keep your website simple or you just want to upload a single
JAR file whenever new versions are released. Loads Jmol somewhat slower
than the previous option, as JmolApplet.jar is all of Jmol, and all of
it must get loaded onto a user's machine before any structure is displayed.
To use JmolApplet.jar either:
a) just put it in the directory containing the HTML page requiring it
and do not use jmolInitialize(), or
b) identify it explicitly in jmolInitialize(), for example:
jmolInitialize("../jmol", "JmolApplet.jar")
JmolAppletSigned.jar
----------------------
The signed version of JmolApplet.jar. This version allows the user to
access files anywhere on a hard drive and from any location on the web.
Typically the user gets a message asking if they want to accept the
"certificate", but this is security feature is not always enabled.
JmolAppletSigned.jar should be used with this in mind. Other than
reading files, Jmol does not currently utilize other capabilities of
signed applets, such as accessing the System clipboard or writing files.
Use only if you know what you are doing and have considered the security
issues.
To use JmolAppletSigned.jar use:
jmolInitialize("../jmol", "JmolAppletSigned.jar")
JmolAppletSigned0*.jar
------------------------
The signed version of JmolApplet0*.jar. This version allows the user to
access files anywhere on a hard drive and from any location on the web.
Typically the user gets a message asking if they want to accept the
certificate for EACH of the 16 loadable files. For this reason,
JmolAppletSigned0*.jar may not be of general use.
To use JmolAppletSigned0*.jar, use the form:
jmolInitialize("../jmol", true)
or
jmolInitialize("../jmol", "JmolAppletSigned0.jar")
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
