On 18 Apr 2007 at 13:12, Bob Hanson replied to Angel Herraez:
> don't forget "display" and "hide" :)
Right; but for now I was just focusing on multi-model and animation.
> >"frame play, frame playRev, frame pause, frame resume"
> >belong in the second group, not in the first. It would be more
> >intuitive to have them moved (or at least duplicated) into
> >"anim play, anim playRev, anim pause, anim resume"
> >
> >I see that some of them are already functional, although undocumented
> >("anim play" with no frame number, "anim playRev" with no frame
> >number, "anim pause", "anim resume" all seem to work, at least in
> >latest version)
I feel that here we have too many options, and some of them overlap. I
would vote to simplify things (I understand that removing some of the
commands raises compatibility problems, but I would go as far as taking
them out of documentation, so they die out slowly).
My idea was that "play", "playRev", "pause" and "resume" should go with
"anim", not "frame"
Right now, "frame play 3" works, but "anim play 3" doesn't ("anim play" does
work).
Plus, as far as I can see, "pause" does exactly the same as "off", and after
that, "resume" does exactly the same as "play". I understand they are
excellent mnemonics, but I'd rather reduce choices --at least, write them
together as synonims--
What are others' feelings?
> frame xxxxx
> model xxxxx
> anim frame xxxxx
> all do precisely the same thing because they use exactly the same code.
Yes, I'm aware of that. For me, I'm just forgetting the existence of "anim
frame" (same rationale as above), and "frame" is *always* identical to
"model" --which is good; there used to be some minor situations where they
were not so--
> Oh, and now there is
>
> trajectory xxxxx
>
> which DOES do something else. (since only one set of coordinates is
> present at any time, you cannot display two models ever with this
> command. It's designed for "streaming" huge sets of coordinates through
> some sort of animation sequence.)
I didn't know about this --and see no doc-- Anyway, that will wait for
another occasion.
> You know, with the new buttons and such, we should be able to write a
> little on-screen in-the-window frame scroller.
Very interesting idea! I'll try to put some time into it; a minimal
functioning
set may be play, pause, rewind, loop, palindrome, once ?. Anyone thinks
playRev is really important in real world --I know it's nice--. Ah! we need
also
one-step forward and backward. An example --using image buttons and
javascript-- is at http://biomodel.uah.es/en/water/
Any ideas?
Thanks for all this hard work and help, Bob. I don't mean to criticize, just
trying to get things sorted out in my mind and check against other users'
thoughts. The sheer volume of commands we have now is so difficult to
hold in memory.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Jmol-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-users
