#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:
use predefined paths
Report Upstream: Workaround found; Bug reported upstream. | Reviewers:
Karl-Dieter Crisman, Steven Trogdon, Punarbasu Purkayastha
Authors: Jonathan Gutow | Merged in:
Dependencies: #11080,#11078,#11503 | Stopgaps:
------------------------------------------------------------+---------------
Changes (by gutow):
* status: needs_review => needs_work
* work_issues: => use predefined paths
Comment:
Replying to [comment:106 jhpalmieri]:
> This passes tests for me. Regarding jmol_scratch: should this be a
temporary directory, or is it important that it persists from session to
session? If it should persist, then `~/.sage/` should be replaced by
`DOT_SAGE`, for example like this:
I think the file should be permanent because it shows the last few console
lines associated with launches of the JmolData.jar process or looking for
the JVM. I was thinking of the file as a size limited log file that can
be used to trace problems associated with JmolData.jar.
I like your suggestion. Sage is big enough that I find I have missed many
predefined values such as DOT_SAGE.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12299#comment:107>
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.
