On Mon, Aug 6, 2012 at 8:46 AM, Gusts Kaksis <gusts.kak...@gmail.com> wrote:
> On 2012.08.06. 16:20, Robert Hanson wrote:
>
>
>
> On Mon, Aug 6, 2012 at 6:38 AM, Gusts Kaksis <gusts.kak...@gmail.com>wrote:
>
>> On 2012.08.06. 14:07, Robert Hanson wrote:
>> It's the same as why do you need an addButton method then :) If you're
>> building a helper library to aid development, it's for the best to add more
>> helpful functions than less. And it's still the same argument between you
>> and me, weather molecule files should be linked with an anchor, which in
>> case of Jmol's/JavaScript's or any other failure would allow the client to
>> download it and view it in, for example, Avogadro.
>>
>>
> That's why we have the WRITE command. But I think you were thinking that
> this would be useful specifically if JavaScript is disabled, not as a way
> to generally download a file. It's not for me to say remove it, only to
> point out its limited usefulness.
>
> In my case, it's the real life scenario - students can (left) click and
> view them in Jmol or right-click and save them on their computer, to do
> some editing in ISIS.
>
>
Of course. Just make sure you only one applet, if possible. As you noted, a
long list of applets is just asking for trouble.
>
>
>
>
>>
>>
>>
>>
>>> The trick with IE8 and 9 is that you have to use XDR (XDomainRequest),
>>> which is basically the same as XHR, just, as usually, the Microsoft way.
>>> And with this jQuery plugin iecors (
>>> https://github.com/dkastner/jquery.iecors) it adds XDR as an AJAX
>>> driver (instead of default XHR), so to speak.
>>>
>>
>> Ah, interesting. Good. Still, that requires sites delivering the proper
>> header.
>>
>> You mean "Access-Control-Allow-Origin: *"? Yes it does, but it's the
>> default cross-domain behavior.
>>
>
> No, it's not. You need that or at least XHR does not work. Absolutely not
> the default behavior. I just recently requested several sites implement
> that, and only after that implementation did the cross-browsing option work.
>
> But it is. It's called "same origin policy" that most of the browsers
> implement. It is to protect clients from malicious javascript code (for
> example, posted by other client in an article comment section) to steal
> cookies or do key/mouse tracking. See here:
> http://en.wikipedia.org/wiki/Same_origin_policy
>
>
Can't access that because Wikipedia is down, but whatever. The point is
that sites without that header are excluded with XHR -- that's what's it's
all about. We must just be miscommunicating, because I know you know that.
> Anyway, nevermind that, as long as it works for 80-90% of users - it's
> good to go.
>
>
Your opinion, not mine.
As for repositioning a div element - it might crash IE, as you remove it
from DOM tree before appending it back - this way destroying Java instance
(but in IE, it seems that it does not kill it completely - same as
display:none). Only option left is to use absolutely positioned Jmol, that
just changes it's position on the page.
I meant on the page, not within DOM.
Bob
-
Robert M. Hanson
Larson-Anderson Professor of Chemistry
Chair, Chemistry Department
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
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Jmol-developers mailing list
Jmol-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-developers
