From: jprocter <Jim Procter>
Date: Tue, 29 Jan 2008 10:32:50 +0000 (+0000)
Subject: groovy from stdin
X-Git-Tag: Release_2_4~135
X-Git-Url: http://source.jalview.org/gitweb/?a=commitdiff_plain;h=79c34bea5d18899696e681e34eebd1c33fc1683b;p=jalview.git

groovy from stdin
---

diff --git a/help/html/features/clarguments.html b/help/html/features/clarguments.html
index 10917b4..8d6a4d8 100644
--- a/help/html/features/clarguments.html
+++ b/help/html/features/clarguments.html
@@ -108,7 +108,7 @@
 		<td>
 		<div align="center">-groovy FILE</div>
 		<td>
-		<div align="left">Execute groovy script in FILE, after all other
+		<div align="left">Execute groovy script in FILE (where FILE may be 'STDIN' to read from the standard input) after all other
 		arguments have been processed</div>
 		</td>
 	</tr>
diff --git a/help/html/features/groovy.html b/help/html/features/groovy.html
index 1a0b83c..3e7b0f4 100644
--- a/help/html/features/groovy.html
+++ b/help/html/features/groovy.html
@@ -7,14 +7,28 @@ language for the Java platform</em>&quot;. The groovy scripting language makes i
 extremely easy to programmatically interact with Java programs, in much the same 
 way that Javascript is used to generate and interact with applets and other 
 objects on the page.</p>
-<p><em>Opening the Groovy Console</em><br>If groovy is available, then the 
+<p><strong><em>Getting Groovy...</em></strong><br>
+Jalview Groovy support is only possible if the core groovy 
+jars which include the GroovyShell are present on the CLASSPATH 
+when Jalview is started.</p><p>The jars are obtained from the 
+<em>embedded</em> directory within the <a 
+href="http://dist.codehaus.org/groovy/distributions">groovy 
+distribution</a>. The easiest way of adding them to the 
+Jalview classpath is to download and build jalview from 
+it's source distribution, and then add the groovy-all-*.jar 
+to the lib directory whose path is given in the java.ext.dirs property.</p>
+<p><strong>Opening Jalview's Groovy Console</strong><br>If groovy is available, then the 
 <strong>Tools&#8594;Groovy Console...</strong> menu entry will be available 
 from the Jalview Desktop's drop-down menu. Selecting this will open the
 <a href="http://groovy.codehaus.org/Groovy+Console">Groovy Console</a> which 
 allows you to interactively execute Groovy scripts within the Jalview run-time environment.</p>
-<p><em>Executing groovy scripts on Jalview startup</em><br>
-The -groovy &lt;script&gt; option on the <a href="commandline.html"/>Jalview command line</a>command line option will </p>
-<p>There is as yet no properly defined scripting interface to Jalview, but all the
+<p><strong>Executing groovy scripts on Jalview startup</strong><br>
+The -groovy &lt;script&gt; option on the <a href="commandline.html"/>
+Jalview command line</a> will execute the contents of 
+&lt;script&gt;. &lt;script&gt; may be a file, or alternatively if it is &quot;STDIN&quot; 
+then the standard input will be used.</p>
+<p><strong>Access to Jalview's functions from Groovy Scripts</strong><br>
+There is as yet no properly defined scripting interface to Jalview, but all the
 public methods of the jalview class hierarchy can be called from Groovy scripts. 
 The access point for this is the <strong>Jalview</strong> object defined in
 the groovy environent which corresponds to the <pre>jalview.gui.Desktop</pre> object which
@@ -30,16 +44,6 @@ def seq = alignment.getSequenceAt(0);
 </li>
 </ul>
 </p>
-<p><strong>Getting Groovy...<br></strong>
-Jalview Groovy support is only possible if the core groovy 
-jars which include the GroovyShell are present on the CLASSPATH 
-when Jalview is started. <p>The jars are obtained from the 
-<em>embedded</em> directory within the <a 
-href="http://dist.codehaus.org/groovy/distributions">groovy 
-distribution</a>. The easiest way of adding them to the 
-Jalview classpath is to download and build jalview from 
-it's source distribution, and then add the groovy-all-*.jar 
-to the lib directory whose path is given in the java.ext.dirs property.</p>
 
 <p>&nbsp;</p>
 </body>