My guess is that the page doing this (maybe local to your computer?) is not
within the http://cancer3d.org
<http://cancer3d.org/structuresChains/3DQWA.pdb> domain. In that case,
Jmol cannot assume that that domain allows AJAX loading across domains.
But it it more interesting than that. The file you are requesting is not a
PDB file. It is HTML:
$ print load("http://cancer3d.org/structuresChains/3DQWA.pdb";)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd";>
<html>
<head>
<title>Cancer 3D </title>
<META name="description" content="A cancer database storing domain
specific mutation information with drug activities in sequence and
structure"><META name="keywords"
content="Cancer,Drug,Activity,Mutation,Structure">
</head>
<frameset rows="100%,*" border="0">
<frame src="http://192.231.106.97/structuresChains/3DQWA.pdb";
frameborder="0" />
<frame frameborder="0" noresize />
</frameset>
<!-- pageok -->
<!-- 01 -->
<!-- -->
</html>
The actual file is at http://192.231.106.97/structuresChains/3DQWA.pdb,
which is likely to be still another domain. So, for one thing, you need to
use the direct reference:
load "http://192.231.106.97/structuresChains/3DQWA.pdb";
and then you need to contact that network administrator and get them to add
the request header:
*Access-Control-Allow-Origin: **
so that you can access it cross-domain from JSmol.
Then, finally, you need to add this JavaScript to any page you access files
from that server from:
*Jmol.db._DirectDatabaseCalls["http://192.231.106.97
<http://192.231.106.97>"] = "%URL"*
so that JSmol knows that that server can send files cross-domain by AJAX.
On Tue, Oct 7, 2014 at 4:43 PM, Angel Herráez <angel.herr...@uah.es> wrote:
> Hi Thomas
>
> What that message says is that to load the 2nd file (probably because it
> comes from a different server) the use of the jsmol.php component is
> needed, and you have not properly configured the location of that file.
> ("your.server.here" is a placeholder for the actual location, that you must
> specify)
> Please see
> http://wiki.jmol.org/index.php/Jmol_JavaScript_Object#Setting_parameters
> http://wiki.jmol.org/index.php/Jmol_JavaScript_Object/Info#Files_and_paths
>
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Jmol-users mailing list
> Jmol-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jmol-users
>
--
Robert M. Hanson
Larson-Anderson Professor of Chemistry
Chair, Department of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr
If nature does not answer first what we want,
it is better to take what answer we get.
-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
