I also agree that having different versions of Jmol offers some distinct advantages. However, I think that its implementation would need very careful planning so that a quagmire of confusion is not created.
On one hand the documentation for Jmol is rather spotty at this time, especially with Bob providing a steady stream of new functions; I could imagine a lot of frustration incurred as users endeavored to sort out which functions operate in different versions of Jmol. Personally, I have continued to implement new functions as I have figured them out, and users may be discouraged from exploring the various capabilities of Jmol is they opt to start with a lite version. I have a couple of ideas about implementing different versions. Would it be possible to keep the popup menu the same for all versions, but merely disable functions that do not work in particular versions? Also, Is it possible to have a single jar file with a command line function that specifies which version of the applet (or particular functions) to send with the web page? This might avoid pitfalls of trying to maintain different versions of Jmol, and allow easy switching between versions by the user. Steve Dr. Steven R. Spilatro Chair, Department of Biology Marietta College ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Jmol-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
