st_launcher

Installation

After this install, you will be able to run scripts using the gemstone and pharo images. The gemstone image is also the default image, so if you want to do development on st_launher itself, you will need to have Rowan and st_launcher installed in a GemStone stone. See GsDevKit_home-based development for additional installation instructions.

The following installation instructions are based on the installation processed that is used for Travis-CI. The environment variable ROWAN_PROJECTS_HOME is used by Rowan as the directory into which git clones will be downloaded. The environment variable ST_LAUNCHER_HOME is currently used by the shell interpreter for st_launcher and needs to be set before running any scripts. When the shell interpreter script is converted to pure smalltalk, ST_LAUNCHER_HOME will no longer be needed.

A GemStone 3.5.0 product tree is installed in $ST_LAUNCHER_HOME/home/platforms/gemstone. A Pharo 7.0.3 product tree is installed in $ST_LAUNCHER_HOME/home/platforms/pharo. sudo is used to install the shell interpreter scripts in /usr/local/bin/smalltalk. This script creates a $HOME/.config/st_launcher directory where the st_launcher image registry (st_launcher_home.ston) will be located:

export ROWAN_PROJECTS_HOME=`pwd`
git clone https://github.com/dalehenrich/st_launcher.git
cd st_launcher
export TRAVIS_SUDO_COMMAND=sudo
export ST_LAUNCHER_HOME=`pwd`/home
bin/install.sh

Examples

The following examples are intended to illustrate different features of st_launcher scripts.

bin/hello.st

Simplest script ... 'hello world' written on objOut (STON write stream). Note that class comment winds up in the help output:

cat bin/hello.st         # view the hello.st source
bin/hello.st -h          # view the help for bin/hello.st
bin/hello.st             # execute bin/hello.st using the default image (gemstone
bin/hello.st pharo --    # execute bin/hello.st using the pharo (headless) image
bin/hello.st gemstone -- # execute bin/hello.st using the gemstone image

bin/error.st

Example error handling ... description written (in red) to stderr. Of course, you can open a debugger on the error:

cat bin/error.st            # view error.st source
bin/error.st --help         # view the help for bin/error.st
bin/error.st                # execute bin/error.st using the default image (gemstone)
bin/error.st pharo --       # execute bin/error.st using the pharo (headless) image
bin/error.st gemstone --    # execute bin/error.st using the gemstone image
bin/error.st pharo -D --    # execute bin/error.st using the pharo image and debug flag (exit pharo without saving)
bin/error.st gemstone -D -- # execute bin/error.st using the gemstone image and debug flag (type quit to exit the GemStone debugger)

ws/array.st

Another objOut example ... with a few different objects:

cat ws/array.st         # vi array.st source
ws/array.st -h          # view the help for ws/array.st
ws/array.st gemstone -- # execute ws/array.st using the gemstone image
ws/array.st pharo --    # execute ws/array.st using the pharo image

bin/listImages.st

Utility script for listing the known images:

cat bin/listImages.st         # view the source for bin/listImages.st
bin/listImages.st -h          # view the help for bin/listImages.st
bin/listImages.st gemstone -- # execute bin/listImages.st using the gemstone image
bin/listImages.st pharo --    # execute bin/listImages.st using the pharo image

bin/about.st

about is an inherited message for all scripts ... useful if you want to know some details about the image:

cat bin/about.st         # view the source for bin/about.st
bin/about.st -h          # view the help for bin/about.st
bin/about.st gemstone -- # execute bin/about.st using the gemstone image
bin/about.st pharo --    # execute bin/about.st using the pharo image

ws/gsClassesAndMethodCounts.st

The class STLObjOutSample was created for this example: classes and their method counts calculated for GemStone and written to objOut:

cat ws/gsClassesAndMethodCounts.st      # view the source for ws/gsClassesAndMethodCounts.st
ws/gsClassesAndMethodCounts.st -h       # view the help for ws/gsClassesAndMethodCounts.st
ws/gsClassesAndMethodCounts.st          # execute ws/gsClassesAndMethodCounts.st using the default image (gemstone)
ws/gsClassesAndMethodCounts.st gemstone # execute ws/gsClassesAndMethodCounts.st using the gemstone image

bin/pie.pharo.st

This script creates a pie chart using Roassal and a headful Pharo image. The data for the pie chart is read from objIn. Here's an example where data produced in a GemStone image, is piped into a Pharo image:

cat bin/pie.pharo.st                                                      # view the source for bin/pie.pharo.st
bin/pie.pharo.st -h                                                       # view the help for bin/pie.pharo.st
ws/gsClassesAndMethodCounts.st gemstone -- | bin/pie.pharo.st pharo-ui -- --label=off # pipe output of ws/gsClassesAndMethodCounts.st into bin/pie.pharo.st and display pie charg

GsDevKit_home-based development

./snapshot.gs.st --dir=./snapshots gemstone.dbf  -- st_launcher_350 -lq
cp -f snapshots/extent0.gemstone.dbf /home/dhenrich/rogue/_homes/rogue/_home/shared/repos/st_launcher/home/images/gemstone/snapshots/