Kind of a doomsday, I'm afraid.
One of the aspects of this (if I have it right, and I think I do) is that *all
Java developers who which to build any applet and run it on their local
installations will have to have trusted signed certificates.*
As far as I can tell, this is pretty much the end of joint open-source Java
applet development. In order to test your code, you will have to have a
*trusted* signed certificate. No self-signing. Period. Of course, you can
still build applications and run them on your computer (go figure!). You
just can't make an applet. We'll see if that pans out, but from what I
read, that's the case.
https://blogs.oracle.com/java-platform-group/entry/code_signing_understanding_who_and
[By the way, this entire blog is something to take a look at. It will be
our guide to the next stage.]
This saddens me very much. It isn't just Jmol. It's about the wider
development community. All except a few will be locked out of contributing
in any significant way to any Java project that involves applets.
Bob
--
Robert M. Hanson
Larson-Anderson Professor of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr
If nature does not answer first what we want,
it is better to take what answer we get.
-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Jmol-developers mailing list
Jmol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-developers
