Let's start a command-line thread. So far I have this: usage: Jmol -o,--noconsole no console -- all output to sysout -D <property=value> supported options are given below -g,--geometry window size 500x500 -h,--help give this help page -i,--silent silent startup operation -n,--nodisplay no display -s,--script script file to execute -w,--write JPG|PNG|PPM:filename -x,--exit run script and exit
The -D options are as follows (defaults in parathesis): cdk.debugging=[true|false] (false) cdk.debug.stdout=[true|false] (false) display.speed=[fps|ms] (ms) JmolConsole=[true|false] (true) plugin.dir (unset) user.language=[DE|EN|ES|FR|NL|PL] (EN) But I suspect that's not really the final story. Here's what I have going: You can get SHOW and GETPROPERTY output isolated and into a file (I'm using "Logger.warn" for the level, so with "set loglevel 3" I can get rid of all the info and just have the warning/errors. I've been able to create JPGs either from the script itself, using a new command write JPG "filename" (Sort of like load XXX "filename") or with that -w command line option. And write CLIPBOARD or -w CLIP work just fine as well. So now it's time to clean this up and figure out what we really want that command line to look like. Bob ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Jmol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-developers
