Nico,
Excellent. Then this will be fun.
[EMAIL PROTECTED] wrote:
It's part of the Jmol application itself,
org.openscience.jmol.app.PovraySaver. So an actual object would be
better (I don't think wee need a specific object, just a
combination of HashMap, Vector, Integer, Boolean, ...) It's
accessible through Export to Povray in the menu.
Right now we have
(Viewer myViewer).getProperty("atomInfo")
(Viewer myViewer).getProperty("bondInfo")
(Viewer myViewer).getProperty("modelInfo")
(Viewer myViewer).getProperty("chainInfo")
(Viewer myViewer).getProperty("polymerInfo")
which all return Hashtable objects.
You can explore what they produce at
http://www.stolaf.edu/people/hansonr/jmol/test/json/property.htm
I realize they are not optimal. I'm trying to think of ways to
make them more usable. With atomInfo and bondInfo you can specify an
atom set. I'm suspecting that for the povray, we should actually
create one called "povrayInfo"
Why don't you outline a data structure, and I'll fill it in.
Bob
--
Robert M. Hanson, [EMAIL PROTECTED], 507-646-3107
Professor of Chemistry, St. Olaf College
1520 St. Olaf Ave., Northfield, MN 55057
mailto:[EMAIL PROTECTED]
http://www.stolaf.edu/people/hansonr
"Imagination is more important than knowledge." - Albert Einstein
-------------------------------------------------------
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&kid=110944&bid=241720&dat=121642
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
