Re: [Jmol-users] Re: [Jmol-developers] doc update -- show

[Miguel <mi...@jm...>]

Bob,

It looks like your updates did not get deployed to the public web site ..=
.
I was unable to find the changes you listed below.

> OK, I have updated some of the script documentation:
>
> http://www.stolaf.edu/people/hansonr/jmol/docs/index.htm=23.color
>
> --includes =22monomer=22
>
> http://www.stolaf.edu/people/hansonr/jmol/docs/index.htm=23.show
>
> --includes
>
>  > show file
>  > show center
>  > show boundbox
>  > show zoom
>  > show transform
>
> http://www.stolaf.edu/people/hansonr/jmol/docs/index.htm=23.set%20(colo=
r%20scheme)
>
> --corrected description
>
> =5Bcomment: =22set colorscheme=22 would make more sense here, I think.=5D=


Not sure exactly what you are saying.

In the future we may extend 'set color' to allow one to change other type=
s
of colors.


> http://www.stolaf.edu/people/hansonr/jmol/docs/index.htm=23.zoom
>
> --better description
>
> In addition, a number of potential functionalities are listed as =22not=

> implemented.=22
>
> Right now I list:
>
> bond --not implemented
> clipboard --not implemented
> connect --not implemented
> display3d --not implemented
> help --not implemented
> list --not implemented
> molecule --not implemented
> pause --not implemented
> wait --not implemented
> print --not implemented
> renumber --not implemented
> save --not implemented
> set backfade --not implemented
> set cartoon --not implemented
> set hourglass --not implemented
> set kinemage --not implemented
> set menus --not implemented
> set mouse --not implemented
> set radius --not implemented
> set shadow --not implemented
> set slabmode --not implemented
> set transparent --not implemented
> set vectps --not implemented
> set write --not implemented
> star --not implemented
> stereo --not implemented
> structure --not implemented
> unbound --not implemented
> view --not implemented
> write --not implemented
>
> Presumably these are of interest for two reasons: (a) people familiar w=
ith
> Rasmol/Chime might be looking for these, and (b) having them there migh=
t
> give developers something to think about.
>
> But they are also a bit distracting. I suspect I got these from scannin=
g
> eval.js. Is it time to remove some/all of them?

I think it is a good idea to leave them in ... for the reasons you cited
above.


Miguel