I was stung by this one too. For reasons I don't understand, pages with Jmol don't stimulate the Inactive Plugin feature but other Java pages do and hence facilitate reenabling of Java plugin. I wonder if there is something we need to improve. If it annoyed Henry and myself it may cause havoc with users.
All the best Nick Sent from my iPad 2 On 21 Mar 2013, at 02:17, "[email protected]" <[email protected]> wrote: > Message: 1 > Date: Wed, 20 Mar 2013 21:47:51 +0000 > From: Rzepa Henry <[email protected]> > Subject: [Jmol-users] Re-enabling Java for Jmol on OS X 10.8.3 > To: "<[email protected]>" > <[email protected]> > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > A recent upgrade of OS X to 10.8.3 disabled Java on Safari (whilst Firefox > remained OK). Turns out the issue was a failure by the Java sub system to > communicate its presence correctly to Safari. If you have seen this > syndrome, it can be fixed simply by visiting > http://javatester.org/version.html and clicking on the inactive plugin box. > Thereafter, Java in Safari is restored. > > Pretty brain dead from Apple: sorry it does seem as if this company really > does not want you to run Java! > > JSMol is certainly getting there, but at the moment for eg surface renderings > and other FPU intensive operations =, JSMol seems around 10 times slower > than Jmol. And on an iPad Mimi it must be closer to 50 times slower (but > it gets there in the end). ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
