User Ratings

★★★★★
★★★★
★★★
★★
3
0
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • JSmol took us out of the bottleneck of Java security restrictions and platforms lack of support. So we can continue developing web materials with the excellent and ever expanding capabilities of Jmol.
  • Easy for use.
    1 user found this review helpful.
  • As a Jmol Web page application developer, one problem has always bothered me. Java browser plugins can be a real nuisance for users. For more than a decade, this nuisance was worth the effort because Jmol was the molecular visualization gold standard. With the decline of the Java browser plugin (There, I said it!), Jmol is still the gold standard for molecular visualization. It simply goes by a different name, JSmol. In a few short months, Jmol developers led by Bob Hanson have produced JSmol. The beauty of JSmol is that it IS Jmol. If the Java plugin tickles your fancy, that's just fine. JSmol will render as the familiar Jmol applet. If on the other hand, you are tired of messing with the Java plugin, then JSmol will render in its HTML5 incarnation. The HTML5 browser rendering of JSmol carries with it almost all of the functionality of the Jmol applet, including Jmol's powerful scripting language. It also brings Jmol's powerful molecular visualization to the mobile device sandbox. Your iPad is no longer limited to "watching the pretty molecule spin." Jmol's evolution as a powerful molecular visualization tool has always been driven by the creative cooperation of developers and users in an open source environment. The key to this cooperation is the powerful scripting language. Users do not have to worry about low level programming. They can develop applications by working in Jmol's high level scripting environment. As a chemist, I have always thought of this scripting language in this way: I do not speak Jmol's language. Jmol speaks my language. This development approach continues with JSmol - JSmol script IS Jmol script. I must admit that I'm happy to free my users from the Java plugin hassle. There, I said it again! I am, however, absolutely excited about moving into the realm of mobile devices. I have no doubt that the historic cooperation between developers and users will lead to some pretty creative things using JSmol in the mobile environment. We're not going to be doomed to simply "watching the pretty molecule spin." Thank you Bob and the development team for all the work that it took to launch JSmol. Otis Rothenberger
  • Previous
  • You're on page 1
  • Next