Metamolecular Products Blog

When using any browser plugin technology, it is important to respond appropriately when the underlying plugin is either not installed or unavailable. This post summarizes the resources available to help ensure your ChemWriter deployments go off without a hitch.

Detecting Java

There are a number of ways to detect Java on a client's browser. One of the simplest and most effective is to use fallback content for the <object> tag. This content gets rendered in the event that a client lacks a plugin capable of responding to the surrounding <object> tag.

Displaying the Applet

JavaScript libraries can make applet deployment much more convenient and less error prone. For your convenience, we offer tips on ChemWriter deployment best practices.

Helping Your Users When Things Go Wrong

Even with fallback content, your users may be uncertain how to proceed. To address this issue, it is very helpful for your site to offer system-specific instructions for enabling Java. The ChemWriter site does this through the gateway link http://chemwriter.com/java. Depending on your browser, you'll be directed to one of four pages:

• Firefox
• Safari
• Internet Explorer 6
• Internet Explorer 7

Conclusions

ChemWriter can be effectively deployed across a diverse array of systems by following some simple guidelines. Using fallback content, properly detecting Java, and offering system-specific help when Java is not available can go a long way to ensuring the best possible user experience.