Adds scripting functionality to Kst.
PyKst scripts can control and share data with a kst session.

ABOUT PYKST
===============================
(The following information is also available inside the svn tree at pyKst/README)

Currently python scripting is implemented. If you are interested in adding Kst support to
other languages, see below.

PyKst (available inside the svn tree at pyKst) is, at the time of writing, not stable
enough for serious use. For the time being, do not write scripts with it except to
test and to send feedback.

Scripting does not introduce any new dependencies to Kst, but PyKst will not run
without certain libraries.

PyKst is tested on Python 2.6 and does not work with Python 3.x.

PyKst needs NumPy 1.6 and does not work with NumPy 1.5. If it is very important
that it should work with NumPy 1.5, modify pykstpp.py to work with the old
API (and submit these changes to kst!!) or send an email to the devel list.

PyKst currently is not portable as pykstpp.py contains C++ code which is
compiled upon first use. It should, instead, create a dynamic library at
Kst compile time. Also, it does not detect the location of the Qt library or
include files, so to get it to compile you might have to modify pykstpp.py.

Please email the Kst list with feature requests and bug reports. I am not able to work on
scripting as much as I have had the chance to do in the past two weeks because of
high school, but can certainly try to help with relatively minor fixes.

The fastest way to get started is to take a look at the examples inside the svn tree
at pyKst/

Documentation is available for now at hen.astro.utoronto.ca/pyKst or inside the
svn tree at pyKst/doc.

DEVELOPPER INFORMATION
===============================
(The following information is also available inside the svn tree at README.kstScript)

Kst implements a client-server interface for scripting. Scripts interacts with a running kst session.

This server is implemented in scriptserver.cpp.

Upon receiving a socket message from QLocalSocket, ScriptServer parses it. ScriptServer implements a map
between command strings and ScriptServer member functions.

These commands include "newVector()", "getPlotList()", etc.

To edit a vector, you would call "beginEdit(Vector Name)". This would open an "interface". One interface
is DialogScriptInterface which simply allows a script to control a hidden dialog. Where speed is important,
other (hard-coded) interfaces are created. To close the interface, one would call "endEdit()".

ScriptServer also implements a very minimalistic language providing:

- if statements in the form:

if(...)
fi()

- variables in the form:
$a=blah
setText($a)

- macros in the form:
newMacro(a,d=c)
setText($a)
setColor($d)
endMacro()

Note that 'c' is not a default argument: they initialize a and d so you can run a macro while writing it.
newMacro(...) runs the macro while it is being written. newMacro_(...) does not)

Note that kstScript (that is, the simple language ScriptServer understands) never uses quotes. It is therefore
important that extra spacing is not added. Comments are also not supported. I feel that it is not worth improving
this 'language'. If someone should have time, a port to javascript would certainly be better.

You can use tests/kstcontrol to write kstScript macros. A list of possible commands is shown inside kstcontrol on the
right hand side. To make macros permanent (i.e., load on start of kst) add them to the file "kstScript.txt".
kstcontrol outputs macros you create to stdout on endMacro().

Writing macros is preferred over implementing them directly in a language (say, python) because the underlying API is
not guaranteed to be consistent and macros allow multiple languages to all have similar functionality with better code
reuse.

To get a feel for how they are written, please see kstScript.txt.

To give a language the ability to communicate with kst, implement functions which use QLocalSocket to communicate with
ScriptServer. Refer to pykst whose source is available in pykst/pykst.py and pykst/pykstpp.py.