I also think that a fixed path is not good.
However, from Nick's quote
# Jmol state version 11.4.4 2007-12-20 06:37;
# fullName = jmolApplet0[343951889313757];
# documentBase = file:/Users/ngreeves/Sites/external/JmolPopup.htm;
# codeBase = file:/Users/ngreeves/Sites/external/;
The
Good point Angel,
The load command also shows different behaviour on a website (Bob's)
or in Dreamweaver.
Web: load /*file*/http://chemapps.stolaf.edu/jmol/docs/examples-11/data/quartz.cif
{1.0 1.0 1.0};
DW: load /*file*/file:/Volumes/nggroup/external/test/histidine.cif;
(this is on Mac OS
Web: load /*file*/http://chemapps.stolaf.edu/jmol/docs/examples-
11/data/quartz.cif {1.0 1.0 1.0};
DW:load /*file*/file:/Volumes/nggroup/external/test/histidine.cif;
(this is on Mac OS X)
Both fixed paths.
Yes. I now remember seing this before, though I don't use state
often.
The
right now, that's an intended limitation of the state functionality. The
EXACT state is saved -- which means the exact files are read. No
relative paths. My conclusions after much consideration, particularly
with Jmol Protein Explorer, is that files read from disk are
problematic, (because,
# message
now goes to the messageCallback queue only, not the console.
But it does sound like a bug.
Eric Martz wrote:
In Jmol applet 11.5.42 and earlier, message xxx displays xxx in
the Jmol console, and also sends it to messageCalback. I use this to
send control marker strings to
# message
oh -- that's when
debugScript is on.
Eric Martz wrote:
In Jmol applet 11.5.42 and earlier, message xxx displays xxx in
the Jmol console, and also sends it to messageCalback. I use this to
send control marker strings to messageCallback that trigger execution
of subsequent code.
I'm expecting this latest I-phone upgrade will open up all sorts of
possibilities. Anyone know what Java is being put on there?
Angel Herráez wrote:
I just found this note in Rich Apodaca's blog:
a piece of software for viewing molecules 3D on the iPhone, including
proteins form PDB!
7 matches
Mail list logo
