This problem with Jmol appears to be multifaceted. 1) The path to Jmol looks strange, although the error messages do appear to come from Jmol. 2) It looks like something is being added to the top of the script file for Jmol and confusing it. 3) Could also related to the JavaVM you are using. Jmol is only tested against the Sun/Oracle VM.
*We are working on patches to Jmol in the present notebook. There are still some asychronicity issues that I think I've almost got a handle on. Let's not try to move this stuff to the new notebook until that is solved. I hope today :) Jonathan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
