That's right. Working within the script mechanism has the permissions;
working within JavaScript does not.
On Mon, Feb 22, 2010 at 11:53 AM, Rolf Huehne <[email protected]>wrote:
> On 02/22/2010 06:33 PM, rob yang wrote:
> >
> >> So you would have to replace the command
> >> 'jmolGetPropertyAsString("image")' by a command to get the file content.
> >>
> >> If you were lucky it would be 'jmolGetPropertyAsString("file")'. I don't
> >> know it. But I am rather sure that there is some way to get the file
> >> information into a Javascript variable.
> >>
> >> The only problem I observed here was the data size. There seems to be
> >> some system dependent security restriction in the amount of data
> >> transferred from Jmol to the browser.
> >
> > Okay, I did try this route, it was
> jmolGetPropertyAsString("filecontents"). As part of the new-age browser
> security, this was actually not allowed by safari and ff3 either (seems to
> be independent of length) either although getting the path of the filename
> was allowed. So it still stands that jmol->server is the only plaussible
> route for me. Thanks Rolf.
> >
> Does the Jena3D snapshot button work for you in the new-age browsers you
> mean? I didn't observe any problems (except with size) up to Firefox 3.6
> and IE8.
>
> So it is likely the specific way
> 'jmolGetPropertyAsString("filecontents")' works that is the problem. But
> there are other ways to get the file data. There is for example the
> "show file" command. At least with PDB files it displays the whole file
> content. You can try if this works with those browsers by typing the
> command into the script input field within Jena3D. Then the file content
> should be displayed in the log area. It might be clipped there because
> the log area has a size limit. Only the last 'n' log lines are shown.
>
> So with a message callback function that parses the file content out of
> the message stream you should be able to get it into a Javascript
> variable. But there might exist other simpler methods.
>
> Regards,
> Rolf
>
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Jmol-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jmol-users
>
--
Robert M. Hanson
Professor of Chemistry
St. Olaf College
1520 St. Olaf Ave.
Northfield, MN 55057
http://www.stolaf.edu/people/hansonr
phone: 507-786-3107
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
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
