Re: [Jmol-users] defining target using Jmol.js

[Eric M. <em...@mi...>]

At 6/6/05, you wrote:
>would it be possible to implement a more user-friendly method for 
>capturing scripting syntax errors in the applet?  or maybe there is a 
>method already in place; I don't know.  it just seems to me that a 
>scripting error could die more gracefully, maybe by showing the offending 
>command.  I don't mind if it halts script execution, but hopefully not 
>kill the entire JVM.


I second this request. When I hand Chime scripts recorded in Protein 
Explorer to Jmol, quite often, I just get a blank Jmol, and I have no idea 
where the first offending command is, or how many there are. (Sometimes I 
can tell where the first one is from the browser status line, but I don't 
have enough experience yet to know whether this always works.)

-Eric


/* - - - - - - - - - - - - - - - - - - - - - - - - - - -
Eric Martz, Professor Emeritus, Dept Microbiology
U Mass, Amherst -- http://www.umass.edu/molvis/martz

Protein Explorer - 3D Visualization: http://proteinexplorer.org
Workshops: http://www.umass.edu/molvis/workshop
Biochem Structure Tutorials http://MolviZ.org
World Index of Molecular Visualization Resources: http://molvisindex.org
ConSurf - Find Conserved Patches in Proteins: http://consurf.tau.ac.il
Atlas of Macromolecules: http://molvis.sdsc.edu/atlas/atlas.htm
PDB Lite Macromolecule Finder: http://pdblite.org
Molecular Visualization EMail List (molvis-list):
       http://bioinformatics.org/mailman/listinfo/molvis-list
- - - - - - - - - - - - - - - - - - - - - - - - - - - */