Tim,
Here are the arguments I would give for stopping the script.
(1) You are certainly going to get an unsatisfactory result.
(2) It is better to have a full stop than to pretend to read a script that
can't really be read.
(3) Programmatically, Jmol "throws an error" and it is simply not possible
to continue from that point. These aren't just warnings -- they are
indications that the script command has failed.
(4) I can see that it might be a pain, but there are a finite number of
differences between Chime and Jmol; when you find "set zoom center" does
not work, and you develop a work-around, you apply that modification to
all scripts and move on. Thus each such inconvenience should be a singular
event. Once you have worked through your list, that should be it, and then
when you get to the end and you have no further script stops, you know
that Jmol is reading the scripts.
Bob
Timothy Driscoll wrote: On Oct 20, 2006, at 10:14 AM,
[EMAIL PROTECTED] wrote: Thank You for this one!!! And
half way on the road. There is a slight drawback with this solution. Each
time my generated script contains an error, detected by Jmol, the
execution stops with a compileError: --* console start *--
sh jmol -ons /tmp/test.mol.spt Executing
script: /tmp/test.mol.spt FileManager opening /tmp/test.mol.spt
compileError(cannot SET:zoom) --* console stop *-- OK,
this is not a file-read issue; it's a chime script issue. There have
been efforts to do this sort of conversion --
http://www.chem.umass.edu/people/cmartin/Jmol/Development/%
20CHIME2Jmol.html comes to mind. But this could be looked at again.
one of my early requests was that Jmol *not* throw a compile error
when it reads an invalid script command (set zoom center is Chime but
not Jmol). it would be much more friendly if Jmol logged the offending
command and continued with the rest of the script. as I recall, Miguel
convinced me that there were good programming reasons not to do this.
in the past, I have set up various kinds of filters to catch and comment
such commands. most of the time, it has been fairly
straightforward, because the commands were all coming through
javascript. since your source is an external file, though, it may be
more tricky to implement. but I can envision a simple server-side
filter, perhaps using perl or php, if you have access to the server. how
difficult would it be to add a scripting buffer to Jmol itself? that
would allow Jmol to strip out or comment invalid commands, without user
intervention. regards, tim
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
