I've had some requests here at Sage Days to switch from the unsigned to the
signed applet when the user asks to do a download of the view they've made on
the page.
To be able to continue using Jmol.js, I came up with the following idea.
1) Unload the unsigned applet saving its state in Javascript (I already do this
for memory management in Sage as people often open up lots of Jmols).
2) Call new public function in Jmol.js that sets the _jmol.archive to
JmolAppletSigned0.jar (Maybe call it jmolToSigned).
3) Reload the Jmol applet using normal Jmol.js calls. At that point the user
will get the warnings associated with the signed applet, but should be
expecting it.
Does anybody see a problem with this idea?
Jonathan
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Jmol-developers mailing list
Jmol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-developers
