Troubleshooting/Applet - Revision history

AngelHerraez: fix missing redirects

2025-08-11T16:54:23Z

fix missing redirects

AngelHerraez: troubleshooting problems with cached files

2017-07-21T15:28:21Z

troubleshooting problems with cached files

AngelHerraez: Firefox has dropped support for plug-ins (and hence Java) in version 52, March 2017

2017-03-15T23:59:12Z

Firefox has dropped support for plug-ins (and hence Java) in version 52, March 2017

AngelHerraez: Chrome has dropped Java support

2015-06-15T15:10:18Z

Chrome has dropped Java support

AngelHerraez: /* Synchronous binary file transfer */

2014-11-15T12:43:47Z

‎Synchronous binary file transfer

Cudo29: /* Problems running the JSmol/HTML5 (non-Java) modality of the Jmol Object in a web page */ Lang templete was added.

2014-10-21T05:35:50Z

‎Problems running the JSmol/HTML5 (non-Java) modality of the Jmol Object in a web page: Lang templete was added.

AngelHerraez: "applet" ==> Jmol

2014-09-07T11:22:06Z

"applet" ==> Jmol

AngelHerraez: synchronous binary file transfer alert

2014-09-07T11:16:40Z

synchronous binary file transfer alert

AngelHerraez: Jmol Object rather than "applet"

2014-09-06T19:51:42Z

Jmol Object rather than "applet"

AngelHerraez: applets blocked per security

2014-08-30T18:00:07Z

applets blocked per security

@@ Line 97: / Line 97: @@
 The rule of thumb is:
 * When the page is run from a local disk, Jmol applet can only open files (load models and scripts) that are in the same folder or below where the applet {{file|.jar}} files are.
-: See [[Jmol_Applet_Deployment_Local|explanation]] and [[Jmol_Applet_Deployment_Local#Examples_of_folder_arrangement|examples]] of allowed and disallowed folder layouts
+: See [[JSmol_Deployment_Local|explanation]] and [[JSmol_Deployment_Local#Examples_of_folder_arrangement|examples]] of allowed and disallowed folder layouts
 * When the page is run from a web server, Jmol applet can only open files that are in the same server.
@@ Line 137: / Line 137: @@
 This is a Java security limitation that only applies to recent Java versions.
 One solution is to use the [[Jmol_Applet#Unsigned_vs._Signed_Applet_.26_Data_Access|signed applet]]. Another may be to set
-[[Jmol_Applet_Deployment_Local#Activating_UseCommandThread|UseCommandThread]].
+[[JSmol_Deployment_Local#Activating_UseCommandThread|UseCommandThread]].

@@ Line 10: / Line 10: @@
 This is harmless; you may disregard it as long as the page works (models are loaded). However, the success may depend on the browser being used.
 It is a warning for the page developer, who may disallow it in the page code using <code>Jmol._alertNoBinary = false</code>
 = Problems running the Java modality of the Jmol Object in a web page =

@@ Line 16: / Line 16: @@
 First of all, wait. Java may take time to load the first time, and the Jmol applet must be downloaded. So, please wait for a while.
 === Jmol is blocked by Java security ===
@@ Line 28: / Line 31: @@
 A yellow square is displayed in the place Jmol should go, with a message inside.
 * Solution:
-Read the message. Either you don't have Java installed, or the browser is configured not to use it. If you are using the Chrome browser, it is now impossible to run applets. Otherwise, try enabling Java for the browser or (re)install Java from [http://java.com/ Oracle's site].
+Read the message. First, make sure that your web browser is one supporting the Java Plug-in (see above). If so, either you don't have Java installed, or the browser is configured not to use it. Try enabling Java for the browser or (re)install Java from [http://java.com/ Oracle's site].
 If you are certain that you have Java installed, there is a chance that the problem is related to certain incompatibility between browser and Jmol versions; the fix is to update the Jmol version used by the page; [[Jmol Applet/Browser Support|read more]].

@@ Line 28: / Line 28: @@
 A yellow square is displayed in the place Jmol should go, with a message inside.
 * Solution:
-Read the message. Either you don't have Java installed, or the browser is configured not to use it. Enable Java for the browser or (re)install Java from [http://java.com/ Oracle's site].
+Read the message. Either you don't have Java installed, or the browser is configured not to use it. If you are using the Chrome browser, it is now impossible to run applets. Otherwise, try enabling Java for the browser or (re)install Java from [http://java.com/ Oracle's site].
-If you are certain that you have Java installed, there is a chance that the problem is related to certain incompatibility between browser (particularly Chrome under Windows) and Jmol versions; the fix is to update the Jmol version used by the page; [[Jmol Applet/Browser Support|read more]].
+If you are certain that you have Java installed, there is a chance that the problem is related to certain incompatibility between browser and Jmol versions; the fix is to update the Jmol version used by the page; [[Jmol Applet/Browser Support|read more]].
 === Black square with an error ===

@@ Line 8: / Line 8: @@
 synchronous binary file transfer is requested but not available
 </pre>
-This is harmless; you may disregard it, the page will work.
+This is harmless; you may disregard it as long as the page works (models are loaded). However, the success may depend on the browser being used.
 It is a warning for the page developer, who may disallow it in the page code using <code>Jmol._alertNoBinary = false</code>

← Older revision		Revision as of 05:35, 21 October 2014
Line 1:		Line 1:
		+	{{Lang:Troubleshooting/Applet}}
		+
	= Problems running the JSmol/HTML5 (non-Java) modality of the Jmol Object in a web page =		= Problems running the JSmol/HTML5 (non-Java) modality of the Jmol Object in a web page =

@@ Line 11: / Line 11: @@
 = Problems running the Java modality of the Jmol Object in a web page =
-== The applet does not show up ==
+== Jmol does not show up ==
-First of all, wait. Java may take time to load the first time, and the applet must be downloaded. So, please wait for a while.
+First of all, wait. Java may take time to load the first time, and the Jmol applet must be downloaded. So, please wait for a while.
-=== The applet is blocked by Java security ===
+=== Jmol is blocked by Java security ===
 Applets in the browser may be blocked per Java security policies. In some situations, you just need to give permissions when a dialog requests to do so, but there are diverse setups and may be more difficult to solve.
 You can find solutions in [http://proteopedia.org/wiki/index.php/Installing_and_enabling_Java Installing and Enabling Java (Proteopedia wiki)], which has step by step instructions for both Windows and Mac OS X, and for the 5 most popular web browsers.
-As a general advice, if the applets are blocked in your browser you should try updating to the latest Java version from [http://java.com/ Oracle].
+As a general advice, if the Jmol applets are blocked in your browser you should try updating to the latest Java version from [http://java.com/ Oracle].
 === Yellow square with a message ===
 * Symptoms:
-A yellow square is displayed in the place the applet should go, with a message inside.
+A yellow square is displayed in the place Jmol should go, with a message inside.
 * Solution:
 Read the message. Either you don't have Java installed, or the browser is configured not to use it. Enable Java for the browser or (re)install Java from [http://java.com/ Oracle's site].
@@ Line 32: / Line 32: @@
 === Black square with an error ===
 * Symptoms:
-A black square is displayed in the place the applet should go, with a message inside: <code>Error. Click to get more information</code>. When you click, a dialog opens:
+A black square is displayed in the place Jmol should go, with a message inside: <code>Error. Click to get more information</code>. When you click, a dialog opens:
   Application error.
   The application could not execute.
@@ Line 46: / Line 46: @@
 [http://jmol.sourceforge.net/jslibrary/#jmolInitialize Instructions for using jmolInitialize() and the Jmol.js library].
-=== Applet disappears in Internet Explorer 9 ===
+=== Jmol disappears in Internet Explorer 9 ===
 See [[Support/Windows#Jmol_pages_in_IE9]]
-== The applet is displayed, but models are not ==
+== Jmol is displayed, but models are not ==
 First of all, make sure you have set the paths correctly for the model files (paths should be relative to the html page; in special ocasions you may also work with absolute paths).
@@ Line 85: / Line 85: @@
 === Models do not load in Linux ===
-On Debian the Jmol application works fine, but the applet refuses to show
+On Debian the Jmol application works fine, but the Jmol applet refuses to show
 the model.
@@ Line 93: / Line 93: @@
 Based on [http://muzso.hu/2012/01/04/network-connection-problems-in-debian-squeeze-after-the-net.ipv6.bindv6only-change some information] about a networking problem of Java.
-== The applet and model are displayed, but further actions have no effect ==
+== Jmol and model are displayed, but further actions have no effect ==
 Symptoms:
 * The initial loading of model --and possibly a script-- works.
@@ Line 112: / Line 112: @@
-== The applet is displayed, other problems ==
+== Jmol is displayed, other problems ==
 === Popup menu does not open and server errors (Fedora) ===
@@ Line 137: / Line 137: @@
 Then open Firefox, select <code>Tools > Addons</code>, and enable the Java plug-in.
-=== Applet does not respond to controls in page (Mac Safari) ===
+=== Jmol does not respond to controls in page (Mac Safari) ===
 <!-- reported Sep.2010 by Jeff Hansen -->
 ''This has been reported in Safari 5.0.1 on Mac OS X 10.6.4.''
@@ Line 144: / Line 144: @@
 The problem was tracked down to the '''AdBlock''' extension in Safari. Disabling the extension removes the problem.
-= Extracting information from the applet =
+= Extracting information from the Jmol applet =
 ''Remember that [[Jmol_Applet#Unsigned_vs._Signed_Applet_.26_Data_Access|the unsigned applet cannot read from or write to]] the local disk.'' Therefore, file operations are excluded; output cannot go to disk, only to the Script Console and/or the Java Console.

← Older revision		Revision as of 11:16, 7 September 2014
Line 1:		Line 1:
		+	= Problems running the JSmol/HTML5 (non-Java) modality of the Jmol Object in a web page =
		+
		+	== Synchronous binary file transfer ==
		+	An alert may be displayed on some pages, depending on the browser you use, saying
		+	<pre>JSmolCore.js:
		+	synchronous binary file transfer is requested but not available
		+	</pre>
		+	This is harmless; you may disregard it, the page will work.
		+	It is a warning for the page developer, who may disallow it in the page code using <code>Jmol._alertNoBinary = false</code>
		+
	= Problems running the Java modality of the Jmol Object in a web page =		= Problems running the Java modality of the Jmol Object in a web page =

← Older revision		Revision as of 19:51, 6 September 2014
Line 1:		Line 1:
−	= Problems running the Jmol ~~Applet~~ in a web page =	+	= Problems running the Java modality of the Jmol Object in a web page =

	== The applet does not show up ==		== The applet does not show up ==