I don't think that's it. As I said, there appears to be something
funny about the javascript that SAGE is using to invoke Jmol. My
normal Jmol pages work fine on FireFox on Windows, MacOS and Linux,
but Jmol in SAGE only works in Safari on MacOS and I've seen
occasional failures on Windows.
Jonathan wrote:
This appears to be a SAGE specific problem. I can even reproduce it
with Firefox on MacOS (works fine in Safari on MacOS). There must be
something about the javascript used to launch Jmol. I will need to
delve into how SAGE uses Jmol... As I haven't looked at this before
On Mon, Sep 28, 2009 at 1:07 PM, Jason Grout wrote:
Jonathan wrote:
This appears to be a SAGE specific problem. I can even reproduce it
with Firefox on MacOS (works fine in Safari on MacOS). There must be
something about the javascript used to launch Jmol. I will need to
delve into how
Bob Hanson (the lead Jmol developer) has verified that replacing
the .innerHTML within a div containing Jmol with plain html does
destroy the applet and free up memory. Thus my suggestion should
work. I haven't got any example clean code yet. I might get to it
this evening, but no promises.
On Sun, Sep 27, 2009 at 11:34 AM, Jonathan gu...@uwosh.edu wrote:
Bob Hanson (the lead Jmol developer) has verified that replacing
the .innerHTML within a div containing Jmol with plain html does
destroy the applet and free up memory. Thus my suggestion should
work. I haven't got any
On Sep 25, 2009, at 10:30 AM, Jason Grout wrote:
William Stein wrote:
We could try changing how jmol is used in Sage as follows: when the
user isn't actively using the 3d image, it is replaced by a static
png. Then there would be at most 1 jmol applet per page.
That seems to be how
A few things related to the memory constraints:
1) The available memory is limited by the set up of the JavaVM on the
users computer. I believe 64 Mb is the default. If you need more you
could supply instructions to the user on how to reset their JavaVM.
There can also be issues with the
This appears to be a SAGE specific problem. I can even reproduce it
with Firefox on MacOS (works fine in Safari on MacOS). There must be
something about the javascript used to launch Jmol. I will need to
delve into how SAGE uses Jmol... As I haven't looked at this before
and have limited time
I have my own answer to #3. I think that using document.write to
replace the applet with a picture when not in use should work. I
haven't investigated yet to see if it really saves memory. My
suggestion is to use the list of applets JmolApplet0,
JmolApplet1, ...JmolAppletn to keep only three
Bug fixes and code changes are documented with some more detail in the
file jmol.properties that can be found in the source code in the
directory src/org/jmol/viewer.
We try pretty hard not to change historical behavior unless it is
determined to be erroneous, so new versions usually work as
Jonathan wrote:
Bug fixes and code changes are documented with some more detail in the
file jmol.properties that can be found in the source code in the
directory src/org/jmol/viewer.
We try pretty hard not to change historical behavior unless it is
determined to be erroneous, so new
On Fri, Sep 25, 2009 at 9:20 AM, Jonathan wrote:
Bug fixes and code changes are documented with some more detail in the
file jmol.properties that can be found in the source code in the
directory src/org/jmol/viewer.
We try pretty hard not to change historical behavior unless it is
On Fri, Sep 25, 2009 at 9:30 AM, Jason Grout
jason-s...@creativetrax.com wrote:
Jonathan wrote:
Bug fixes and code changes are documented with some more detail in the
file jmol.properties that can be found in the source code in the
directory src/org/jmol/viewer.
We try pretty hard not to
William Stein wrote:
We could try changing how jmol is used in Sage as follows: when the
user isn't actively using the 3d image, it is replaced by a static
png. Then there would be at most 1 jmol applet per page.
That seems to be how mathematica does things. At least, when I have
Hi Bill,
On Fri, Sep 25, 2009 at 1:14 PM, Bill Page bill.p...@newsynthesis.org wrote:
Unfortunately there is no change in behavior with this update. It
still works fine for me on my Linux clients and when using Windows
Vista, but on a slightly older laptop running Windows XP (up-to-date
On Fri, Sep 25, 2009 at 2:35 PM, Alfredo Portes wrote:
On Fri, Sep 25, 2009 at 1:14 PM, Bill Page wrote:
Unfortunately there is no change in behavior with this update. It
still works fine for me on my Linux clients and when using Windows
Vista, but on a slightly older laptop running
On Fri, Sep 25, 2009 at 10:30 AM, Jason Grout
jason-s...@creativetrax.com wrote:
William Stein wrote:
We could try changing how jmol is used in Sage as follows: when the
user isn't actively using the 3d image, it is replaced by a static
png. Then there would be at most 1 jmol applet per
William Stein wrote:
In our case, it sounds like we would have to wait for a round trip to
the server every time we tried rotating things? (or maybe we'd wait a
few seconds, and then replaced it?)
I can't see why a roundtrip to the server would be needed.
Can you unload a java applet and
On Fri, Sep 25, 2009 at 5:15 PM, Jason Grout
jason-s...@creativetrax.com wrote:
William Stein wrote:
In our case, it sounds like we would have to wait for a round trip to
the server every time we tried rotating things? (or maybe we'd wait a
few seconds, and then replaced it?)
I can't see
On Thu, Sep 24, 2009 at 12:52 PM, Jason Grout
jason-s...@creativetrax.com wrote:
I updated the jmol spkg to 11.8.6 at #7003 (ready for review!).
I just want to comment that I want jmol to just be part of the
standalone sage notebook.If you look in the
sagenb/data/java
directory of
Jason,
What are the Sage version prerequisites for this package (if any)?
Besides new features is there a list of bug fixes? In particular, do
you know if this version solves the problem with jmol on some Windows
XP systems that has been mentioned occasionally here on this list?
Regards,
Bill
Bill Page wrote:
Jason,
What are the Sage version prerequisites for this package (if any)?
Besides new features is there a list of bug fixes? In particular, do
you know if this version solves the problem with jmol on some Windows
XP systems that has been mentioned occasionally here on this
22 matches
Mail list logo
