Step

Comments

Windows 2000, XP

Mandrake Linux 10.2, Mac OS X

1

The Java Runtime Environment will be sufficient if you don't plan to write any Java code AND you're using Windows. Otherwise  you need the Java Development Kit

You should obtain something like this:

java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)

2

You need to install XSB Prolog

Write down (or copy into the clipboard...) the paths for the directories containing the executable images of Prolog. We'll use this below to define the XSB_BIN_DIRECTORY environment variable. 

These will typically be something like

XSB_DIR...config.....bin

3

Look into the windowsScripts directory. Edit windowsVariables.bat, changing the variables JAVA_BIN, XSB_BIN_DIRECTORY to the values you got in the install steps above

Look into the unixScripts directory. Edit unixVariables.sh, changing the variables JAVA_BIN, XSB_BIN_DIRECTORY  to the values you got in the install steps above

Mac OS X note: uses some different system directory arrangements take a look at MacOSXVariables.sh for inspiration

Make sure the script files are executable:
chmod a+x *.sh

That's it :-) 

See if it works by running a run....listener.bat scripts (./run...listener.sh in Unix). A Java window with a Prolog listener should appear, looking perhaps like this:

Alternatively, you can try the Sudoku puzzle editor/solver (change directory separators to / under Unix)

%JAVA_BIN%\java  -DXSB_BIN_DIRECTORY=%XSB_BIN_DIRECTORY%  -classpath ..\interprolog.jar com.declarativa.interprolog.examples.SudokuWindow

See the sources in com/declarativa/interprolog/examples for more information; subdirectory SudokuPuzzles contains... puzzles, in a simple Prolog format.

You can optionally run the standard test suite, using the script testit; when finished successfully (after about a couple of minutes in a 400MHz Pentium) the following window will appear:

If things don't go well: first make sure the steps above were done properly; then open a command shell window, cd to the interprolog212 directly, run the failing script with -debug afterwards, and email the console log to interprolog@declarativa.com

For example, to make runXSBSPlistener.bat report debugging information edit the command line to

%JAVA_BIN%\java -classpath %CLASSPATH%;..\interprolog.jar com.declarativa.interprolog.gui.XSBSubprocessEngineWindow -debug

4

Using it

Try some Prolog goals, such as browseTerm(vp(np(interprolog),verb(working))), which should display a tree. You may drag your Prolog source files into the listener window for consulting, or use the menu "File/Consult" . Edit the files with you favorite editor.

Some documentation:

• Java: Tutorial, Reference (your JDK installation may include this)
• Prolog: 
  • XSB Manual 1 and XSB Manual 2 (your XSB installation will typically include a Postscript version)
• InterProlog: introductory paper, Java-side API, Prolog-side predicates, FAQ. See also the CHANGES.txt file, and comments in sources.