> > Q: Do you know which .jpg files were saved as progressive? > > I think all in org/openscience/jmol/images/*.jpg were. It wasn't clear > which of them was actually crashing the JVM (not just an exception but a > full-blown crash), so I saved all of these JPGs with progressive disabled, > repackaged, signed the JAR and the crash was avoided.
There were only 4 .jpg files. I saved them all as non-progressive and checked them in to CVS. > > Q: If there are no negative implications for local usage then why do we > > need both? Why not just sign the Jmol.jar file and be done with it? > > Two reasons: > > 1. to avoid the bug mentioned above in older JREs (someone might add new > JPGs to the JAR that trigger this bug - we should be using PNGs actually) > > 2. for those who want a smaller (marginally faster to load) application > JAR I decided to take the other path. Jmol.jar is now signed using the same certificate as JmolAppletSigned*.jar This should simplify your WebStart deployments. Miguel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Jmol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-developers
