X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=doc%2FAddingGroovySupport.html;h=5dfa54fd2ac5a1835ed22522876fbb89a4ff2c00;hb=d5f02d0f3e1a6a9767ef065ebe8f56902c041a33;hp=e18e273bc6e63d17a8266460e4a4915b193850f3;hpb=6ab4ef1cc71ff9d28a21a139db69e4a8351a3fb5;p=jalview.git diff --git a/doc/AddingGroovySupport.html b/doc/AddingGroovySupport.html index e18e273..5dfa54f 100644 --- a/doc/AddingGroovySupport.html +++ b/doc/AddingGroovySupport.html @@ -1,7 +1,7 @@ +Adding Groovy Support to Jalview + + +

+Adding Groovy Support to Jalview +

+

+There is currently no scripting language +extension within Jalview, in part because a +scripting API has not yet been developed. +

+

It is, however, really easy to embed scripting +engines like groovy. If groovy is detected on the +classpath, a new menu entry on the Desktop's Tools +menu will open the GroovyShell. +

+

Here are some scripts to get you started:

+ +

Getting Groovy...

+

+You need the core groovy jars which include the GroovyShell. The easiest way of doing +this is to add the groovy-all-*.jar to the lib directory whose path is given in the java.ext.dirs property.

+

The is obtained from the embedded directory within the groovy distribution). +

+

TODO

+

+Using Java class methods from Groovy is straightforward, but currently, there isn't a set of easy to use methods for the jalview objects. A Jalview Scripting API needs to be developed to make this easier.

+

Making it easier

+

jalview.bin.JalviewScript could be a top level jalview instance of a script execution thread, creating and maintaining the context for scripts operating on the jalview datamodel and interfacing with the Jalview GUI. +

+ + +