On Jun 25, 2006, at 7:49 PM, Bob Hanson wrote:
> you need to invoke Viewer.refresh() manually using
>
>   jmolGetPropertyAsJavaObject("jmolViewer").refresh()
>
> Or you can just use
>
>   jmolScriptWait("")
>
> because a script automatically refreshes at the end.

ah i see. i was hoping it was something simple like that.

> --My method is decidely low tech and not necessarily to be  
> recommended if someone else has a smarter approach:
>
> 1) I use Build.xml within Eclipse, including "clean" reordered  
> before "main" if I've messed with JmolConstants or did anything  
> that might affect any interface or just before an upload. This  
> creates the Jar files in the main workspace directory.
>
> 2) I use the test HTML files you see in http://www.stolaf.edu/ 
> people/hansonr/jmol/test/proto to test all applet code. The idea  
> here is to document all tests in relation to any particular topic  
> so that I can run through them all quickly. I often find where I've  
> broken one thing to fix another this way.
>
> 3) I have a little DOS batch file that copies the JAR files from  
> the Eclipse workspace to my working HTML directory. I always call  
> it "t.bat".
>
> So I do the build, and when I see "BUILD SUCCESSFUL" I exit the  
> browser (otherwise any new JAR file is not loaded), switch to DOS,  
> type "t", and I'm testing.
>
> Generous use of
>
>  System.out.println(...)
>
> gives me the feedback I need. Also, the following script commands  
> are useful:
>
>  set debugScript
>  set testFlag1
>  set testFlag2
>  set testFlag3
>  set testFlag4
>
> Those test flags you can check using viewer.getTestFlag1(), ...2(),  
> etc., so you can test different options if you want to.
>
> I realize this is back to the "no breakpoint" methods of  
> yesteryear, but it works for me, and the HTML files I use for  
> testing allow for very quick retesting of scripts, and also end up  
> being demonstration pages, so I figure that makes up for the  
> nuisance of no breakpoints.

no, that's rather useful actually. it reminds me of junit.

if you're ever curious, there's a way to add breakpoints to applets  
embedded in pages, which i discovered after my request for help.  
particularly useful if you can tell what is breaking but not why.

also, what about bonds? are those going to need to be updated as well  
when atom coordinates are changed? is there anything else like this  
that might?

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers

Reply via email to