>> Q: How does one specify XYZ coordinates?
>
> Right now you just start listing decimal numbers:
>
> draw line 1.0 1.0 1.0   2.0 2.0 2.0
>
>
>>
>> Q: Are they just 3 numbers, or do we use some type of encapsulating
>> syntax? ... as in [x,y,z]
>
> I decided for now not to fool with the compiler, so no commas, no
> brackets.

Good decision

> We could imagine a general (x,y,z) compilation that looks like
>
> coordinateBegin
> x
> y
> z
> coordinateEnd

The compiler would have problems with this ... because an open parenthesis
can currently be used to indicate the start of an atom expression.

> sort of like
>
> expressionBegin
> ...
> expressionEnd
>
> I'm not sure that's really necessary, though.

OK. If you are satisfied with 3 separate coordinate values then it is fine
with me.

> It looks like what I have up right now has a bug that makes it so you
> MUST show a percent scale if you are using coordinates.
>
> draw line 100   1.0 1.0 1.0   2.0 2.0 2.0

Do not understand.

> I was having a problem with scale because I wasn't specifying which
> mesh it referred to. So I guess I still don't quite have that. I'll
> have to fix it.
>
>>
>> Q: What is the relationship between a drawn object and models/frames?
>> Can
>> an object exist in more than one frame?
>
> haven't thought about that. My guess is that it is totally messing up
> on that front. Right. Hmm. Say you have an animation. I could imagine
> wanting to see the line between two atoms move with the animation,
> like the way I set up measure. Oooh, yes, that could be interesting.

Yes, that is what I was thinking.

> Or you might want to specify the model. Or you might want to specify a
> fixed plane and then watch the animation move through it, for example.

Correct. If your parameters are fixed then it will sit still while the
animation moves.

Please give some thought to a mechanism whereby we can specify the models
where an object is displayed.

> Looks like I might need some keywords here. This certainly suggests
> challenges await the naive.
>
> I see that pmesh is NOT model-specific. Probably makes sense, because
> those tend to be so mamouth. My idea here is to present fairly small
> elements -- just a few points -- not huge geodesics.

Correct.


Miguel



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers

Reply via email to