#9238: J. Gutow's update to Jmol in the notebook...
------------------------------------------------+---------------------------
   Reporter:  gutow                             |       Owner:  gutow       
       Type:  enhancement                       |      Status:  needs_review
   Priority:  major                             |   Milestone:  sage-4.7    
  Component:  notebook                          |    Keywords:              
     Author:  Jonathan Gutow                    |    Upstream:  N/A         
   Reviewer:  Jason Grout, Karl-Dieter Crisman  |      Merged:              
Work_issues:                                    |  
------------------------------------------------+---------------------------

Comment(by kcrisman):

 Third try... some comments from heavier testing.

  * For me, command line does not work.  I get a jmol window with 'zapped'
 and some other error message about a .sage/temp/....jmol file.  This could
 be because I just dragged in the files from the jmol spkg, but I wanted to
 be able to create a new sagenb spkg.  But changing the jmol script as
 indicated above didn't seem to help this.

  * Regular use seems to perform as advertised.

  * Jason's patch is necessary, works great.  However, it's worthless
 without changing that sleeping to a link to wake up, as Jason said, since
 not everyone will associate 'advanced' with waking up.

  * The smaller sizes don't seem to work so well with that patch.  It's
 hard to see what I mean until you try it.  It's possible for the miniature
 size to almost completely disappear.  Try spin on with that size - you'll
 get something coming in and out of view.

  * Heavy use is another matter.  I can get ALL kinds of horrible crashes
 (such as the ones that twice killed this comment, until I wised up and
 used a different browser for Trac) and other errors, some of which
 occurred above, others are new.

 The worst was when I was trying to open the page with 6 or 7 jmols, none
 of which I had evaluated, but were left over from earlier openings of the
 worksheet, and I tried to evaluate another cell and got a Java exception
 window that would not close, would not let me change focus to another
 browser window, and was completely full of security exceptions I did not
 understand.  Wow!  So we probably need to encourage people to be CAREFUL
 with this still.

 Interestingly, Chrome wouldn't even let me open it (and said, `Aw, snap`
 when it failed) because it spotted the problem early!  Actually, I find
 this to be a bug, because I never did open it, which didn't happen with FF
 and Safari.  It doesn't give the chance to just kill the script but still
 open the page.  Weird.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9238#comment:74>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to