(this probably should go to the developer list -- Eike, are you on that?) Please feel free to experiment with this. Let me know on or off list if you need any assistance. One thing that is not necessarily optimal in Jmol is that processing occurs DURING script evaluation -- if there is an error, say, at word 6 of "isosurface", then it is possible that you will get a partially rendered isosurface. It's just the way it was done.
However, if you really wanted to work on this, I think it could work. What you would do is write a class extension to Viewer and make your test "viewer" an instance of that. All actions by Eval run through Viewer methods, so all you have to do is create different versions of those particular methods in your test version. You could have them do anything (or nothing), as you wish. And certainly there's no need to render anything. As a start, we have: synchronized public String scriptCheck(String strScript) This method does just the compilation, and checks for: a) improper syntax involving punctuation and operators. b) invalid commands. c) improper atom specifications. So that's a lot already. But it has a flaw in that it passes "unimplemented" commands to Eval right now. Actually, I think this could be fixed without too much hassle. public void setAppletContext(String htmlName, URL documentBase, URL codeBase, String appletProxyOrCommandOptions) This method allows you to set runtime parameters such as running silently, running "headless" (turning off all frame rendering), etc. That is, you can ALMOST do exactly what you describe now. Bob > > My first approach (obviously?) was to look into the process flow implemented > by Jmol and then write a wrapper to reuse those classes and methods. That > is > run the same tests as in the Jmol check on "compiler" level and evaluation > level. But as i figured out this might be impossible right now. > E.g. in "Eval.java" an instance of "Viewer" is required, IIUC. > > >> I don't think it's feasible to change this. So let's >> figure out how to work with what we have. > [...] >> I think the primary request here was for a non-applet solution. But if > > Indeed; my aim is to implement a java tool (syntax checker) that may run as > a standalone (batch job / ant task) application as well as being inserted > as > a filtering component on the server side *and* uses the same tests as Jmol. > > Regards > EJ > -- > Eike Jordan <[EMAIL PROTECTED]> > > | FIZ CHEMIE BERLIN > | Franklin Str. 11 ------ ,__o > | 10587 Berlin ------ _-\_<, > | ------ (+)/'(+) > | Tel. : 0049-30-39977 214 > > > ------------------------------------------------------------------------- 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-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jmol-users > ------------------------------------------------------------------------- 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-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-users
