From: Miguel <mi...@jm...> - 2005-11-28 14:12:15
|
> The switch to Jmol is easy because all users have got a JVM on their > computers, except with recently shipped IE versions. Microsoft has not shipped their JVM since the fall of 2002. They announced that they were dropping support for it some time earlier. Newer versions of Windows XP cannot install the Microsoft JVM. > In the high schools and colleges I work in, I did not have to bother th= e > IT responsible to get specific program installed on the computers befor= e > bringing my classes in computer labs. It is still the case that the vast majority of machines have the JVM installed and that no explicit IT support is required. Dell, HP/Compaq, and IBM have all shipped with the Sun JVM pre-installed for several years. With recent prereleases of Jmol.js, any Windows machine that does not hav= e the Sun JVM installed will automatically prompt the user for a one-time installation of the Sun JVM. > Recently I took also part in setting up a website aimed at gathering an= d > sharing molecular datas for french biology-geology teachers (you can > have a look at http://librairiedemolecules.education.fr, and for the > implementation of Jmol an exemple at > http://librairiedemolecules.education.fr/vismol.php?idmol=3D11 ). I fou= nd > Jmol to be an awesome replacement for chime because most of the users > can have a straight access to the molecular models without having to > install any specific software. Good > This is exactly what we need for people > to become more familiar with molecular visualisation before using it in= > class. I agree. I do not believe that we have any hard data to know which Java virtual machine these people are using. My hope/expectation is that the vast majority of Windows users are alread= y running with the Sun Java Virtual Machine. Of those who are not, the vast= majority can easily be upgraded ... Jmol.js will automatically install it= , others need to make a one-time visit to www.java.com I think your fear is that many users have older systems that are still running the Microsoft JVM and that the one-time installation of the Sun Java Plug-in will be too difficult. We do not have any hard data. > If the next Jmol version is not going to support the older JVM, I think= > that I will propably not move to this new version for a while and stay > with the current one. I assume that the old version would remain available. Please quantify 'a while'. Q: Would one more year be sufficient? > Do you think that if that change happens it would be possible to keep > the current version (development frozen) and using a test at startup > redirect old JVM to this version instead of the new one ? No, this would not be possible. Let's keep talking. Miguel |