G'day, After recently upgrading our site's JmolApplet from v10.0 to v11.6 I noticed an increase in the time taken by v11.6 during initialization, i.e. prior to rendering. In practice this is not a problem as it's a matter of less than one second vs. one to two seconds.
I only noticed the difference because we have a web-page that displays dozens of JmolApplets - then the difference becomes a few seconds vs. tens of seconds. This is not a complaint, far from it, merely an observation (arising from a pathological example) that might otherwise have gone unnoticed. It lead me to wonder whether JmolApplet's initialization has been profiled? Perhaps there are (large) objects whose initialization can be delayed, e.g. lazy instantiation/initialization (also having memory usage benefits). Regards, Chris. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
