I put up a new test page with a series of link to recreate the mouseover
effect. It's at the same URL :
http://librairiedemolecules.education.fr/outils/test/test.htm
My feeling is that it works quite satisfactorily.
The time lapse between each script is 100ms with the useCommandThread directive
(Mac safari and firefox).
Without the useCommandThread directive, it's 2ms with safari and 100ms with
firefox
Surprisingly, both navigators don't behave the same way in respect with
scrolling (instead of hovering) over series of links : the mouseover event if
fired for each link under firefox, whereas it's only fired once in a while
under safari, the later behaviour giving the feeling of a more responsive
interface.
I guess that if I ever design a script stacking function, I could live with
discarding all the scripts fired by the onmouseover events but the last one.
-Paul
Le 24 juil. 2010 à 21:21, Paul Pillot a écrit :
> I didn't explain myself properly. In fact, the stacking process would issue
> all the non-processed script at once in the same script separated by
> semi-colons, and maybe by a very short delay to give the illusion of
> successive scripts.
> I haven't tried yet the signed applet with the new 50ms delay, will keep you
> informed of my progress
> -Paul
>
> Le 24 juil. 2010 à 20:00, Robert Hanson a écrit :
>
>>
>>
>> On Sat, Jul 24, 2010 at 2:00 AM, Paul Pillot
>> <paul.pil...@ac-orleans-tours.fr> wrote:
>> I think I will implement a kind of script stacking, that would store pending
>> scripts while the applet finishes the current script and would fire the
>> pending scripts in one row, afterwards.
>>
>>
>> Oh, I wouldn't recommend that. It would be very difficult to manage and
>> would just be complete overkill. That is precisely what Jmol is already
>> doing -- all the scripts enter a queue and are processed only after the
>> previous script is complete. So I can't imagine that you could do any more
>> than that, except slow that process down. You might remember that that was
>> one of my first contributions to Jmol, which fixed a vexing problem where
>> scripts were running at the same time rather than sequentially.
>>
>> Exactly what you suggest, by the way, is implemented in Jmol Protein
>> Explorer -- See http://chemapps.stolaf.edu/pe/protexpl/js/top_func.js -- so
>> look there if you must -- but really, that was all designed by the ingenious
>> Eric Martz prior to my introduction of the script queue business. In the end
>> it turned out to be sort of useful -- it now allows me to use the signed
>> applet as a "proxy server" for getting the text of any web page into
>> JavaScript -- something that otherwise requires AJAX. And that is how we get
>> the Proteopedia Wiki entries in there.
>>
>> Bob
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
