> I am wondering if it violates your design principle to make > getGraphics3D() public through the JmolViewer > interface.
Well, I don't think I am opposed to this ... for Java programs. > One can then render extra objects not currently supported > through scripts by routing through > this method. Yes ... the g3d routines are already public. You should be advised that I am planning some changes to g3d. In particular, I am trying to eliminate any use of java.awt or javax.swing methods in order to make the Jmol viewer operate under the Eclipse SWT. I plan to define an interface org.jmol.JmolWindowingEnvironment that will have AWT, Swing, and SWT implementations. I expect this to have an impact on the initialization of the Jmol viewer and of the g3d package. But it should not have any impact on the other public methods. > P.S. I am attaching a screenshot of a 2D molecular dynamics simulation > showing a hypothetical nanoconveyor > so that you can see what I meant in the previous email. Very nice! 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
