#12299: Advance Jmol Interactive Features in Flask Notebook
-------------------------------------------------------+--------------------
Reporter: gutow | Owner: jason,
mpatel, was
Type: enhancement | Status:
needs_work
Priority: major | Milestone:
sage-5.2
Component: notebook | Resolution:
Keywords: Jmol, 3D, notebook | Work issues: pop-up
menu?
Report Upstream: Reported upstream. No feedback yet. | Reviewers:
Karl-Dieter Crisman, Steven Trogdon
Authors: Jonathan Gutow | Merged in:
Dependencies: #11080,#11078,#11503 | Stopgaps:
-------------------------------------------------------+--------------------
Comment (by kcrisman):
> My first attempt at getting this to work showed that
> * the Tachyon "placeholder" evaluates fine, though I agree with strogdon
from #9238 that it's annoying to always have to make it interactive,
though I understand the reasoning
You were right, it was the Jmol placeholder. I really find that annoying.
> * Nothing else worked - lots of messages about restarting Jmol and so
forth. At one point I even got a !JmolData java applet starting outside
the browser window.
> Too late now to see what I did wrong, but wanted to let you know all was
not flawless :( sorry.
I had the same problems on the same worksheet. This worksheet had only
five Jmols, but took a million years to load (well, over a minute) and
then I get the following.
{{{
Jmol Applet #0 is having trouble loading. Will retry once.
Second attempt to finish launch of Jmol Applet #0 failed. Recommend
reevaluating the cell manually.
}}}
Same for all Jmols. Some didn't even make the static images. Even re-
evaluating doesn't help at all - it does create the image, but as soon as
I make it "live" I get the same horrible messages.
Note that in the new worksheet, I am just fine, and the little Jmol logo
shows up properly in the upper left corner - not ever in this old
worksheet, or only with the briefest of appearances. Notice that in old
'''interacts''' everything works fine, presumably because these are indeed
newly generated!
----
Question about implementation. How much work does Jmol have to do to
generate all those static images '''every''' time that one opens a
worksheet? In theory, once there is an image (png, I guess) generated, it
should just stay in the cell's folder and be displayed; we certainly don't
want to create a new one each time, any more than we do this for 2D plots.
Though even with a largish sheet it doesn't seem to take super long, a
little delay.
Have you tried using this on "old" worksheets with Jmols? This seems to
be the problem I have, consistently; any Jmols from the old notebook (by
which old Jmol is presumably meant) don't work.
----
More minor issues.
* When I sleep an image, it doesn't come back with the advanced controls
if I had them up. Is there any way to "save" that state, or is it too
hard?
* Although it's pretty clear by the content, it's a little hard to see
which tab you are on in the advanced controls sometimes. Maybe the
shading could be slightly different.
* In interacts, I think there is no point to having the initial static
image. I have no idea if there is a way to detect this, but presumably
one wouldn't have asked for this to be evaluated if one wasn't going to
use it.
* The opening of the "JmolData" app each time is a little annoying.
* When doing
{{{
implicit_plot3d(x^2+y^2+z^2==16,(x,-5,5),(y,-5,5),(z,-5,5),color='green',plot_points=200)
}}}
I got
{{{
viewer handling error condition: java.lang.OutOfMemoryError: Java heap
space
}}}
Maybe I'm being overoptimistic; the docs don't even have any with 100
`plot_points`.
* On the plus side, the thing where only four Jmols are active at a time
is working fine. I notice that it deactivates the one furthest down or
something, not the oldest one.
----
I have to say that I'm by far the most concerned about the "old
worksheets" issue. Second is the "automatically every image is static" -
couldn't at least the ''first'' one be "live"? - but nearly everything
else could be considered an enhancement request. Let me know what stuff
I've mentioned is worth discussing here.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12299#comment:32>
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.
