Jmol'ers,
I've just started playing around with the new JmolAPI.js, etc. setup for Jmol
13.0. I really dig most of it; although I was initially intimidated, I like the
increased modularity and the obvious increase in flexibility it provides.
My question is about the alert that appears when using the signed applet. When
I set isSigned to true in the "Info" object (I call it "jmolOptions") and
specify JmolAppletSigned.jar as the jarFile, I see an alert along the lines of
"Do you want to use the signed applet? This could pose a security risk…etc."
This appears each time the page loads, preventing the user from selecting an
option along the lines of "Always trust applets from this publisher" to prevent
further intrusions.
Bob: I know there's a way to get around this, because when I visit your example
page, I see no warning at all—and you're using the signed applet! ;-)
http://chemapps.stolaf.edu/jmol/docs/examples-12/simple2.htm
I know it's probably something simple and stupid…but I have scrutinized the
example page's code, as well as JmolCore.js and JmolAPI.js to no avail. I've
tried both inline and $(document).ready() approaches. What am I missing?
Cheers, Mike
------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
