William, I guess I would like to know which of the problems you refer to still are a problem in the updates to Jmol that are awaiting review?
The things left that I know about are: 1) The way Jmol functions in interacts is a problem, but this has nothing to do with Jmol. It is the way the interact code is written. The interact code insists on reloading the whole applet every time the server does a recalculation, rather than just send the applet a command to load the recalculated graphics file (this would get you a factor of 10 - 100 in response time). 2) Jmol will not work on iOS. There is a way to get it to work on Android, but we cannot look at that until Sage upgrades to a much more recent Jmol (also awaiting review). A temporary fix is to generate static 3D images and not load the applet unless the user wishes to make them interactive (also in the updates awaiting review). I also agree that you should be looking at supporting other rendering methods as the world of web interfaces is constantly shifting. Jonathan On Jan 28, 12:15 pm, William Stein <wst...@gmail.com> wrote: > Sorry to trouble you, but I think it is time to move past jmol. We could > keep jmol as an option indefinitely... but i do not think it should be the > default for 3d. It is not robust enough, and it is very, very > frusratingly non-interactive: despite many attempts i have never seen a > compelling demo of genuine sage <----> jmol interaction. Three.js will > make this possible; it will make it easier for prople take 3d images from > sage and put them in their own web pages (much more lightweight), supports > ios and android -- which is *hugely important* - etc. > -- > William Stein > Professor of Mathematics > University of Washingtonhttp://wstein.org -- 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
