Studio Download and installation

From InterProlog Wiki
Revision as of 04:14, 22 October 2014 by MiguelCalejo (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

(links below for version 1.0beta1, aka r476, October 17 2014)

Being a Java application dependent on an external language system – XSB Prolog – Prolog Studio tries nevertheless to be as "installation-free" as possible, so users can dive into it quickly.

Installing on Windows

Alternative A: use our Windows fat zip file

  1. Download the fat zip that includes XSB
  2. extract its contents into a new folder
  3. doubleclick the interPrologStudio.jar file.

Alternative B: use XSB Windows installer

Installing on Mac

  1. Download a self-contained zip file (which includes Studio, plus a recent compatible and pre-built XSB engine),
  2. extract its contents into a new folder
  3. doubleclick the interPrologStudio.jar file.

Linux and harder alternative for Mac

This is intended for people who build and/or install their own XSB Prolog:

  1. Make sure you have a compatible XSB Prolog (built from from May 2014 or later) installed on your system
  2. Download interPrologStudio.jar into a new (writable) directory
  3. doubleclick interPrologStudio.jar, and in the upcoming dialog please indicate where your XSB Prolog executable is

If the last step does not work, open up a shell window, cd to the interPrologStudio.jar directory and:

  • java -jar interPrologStudio.jar
  • ... then, when asked with a dialog, indicate where your XSB Prolog executable is

If things go bad

If something goes wrong during startup, Prolog Studio should detect the problem and refuse to run, presenting an error dialog; or it may even draft an email bug report.

Btw: if something goes wrong later, try to use Studio's bug reporter. It's in the listener window, Tools/BUG REPORT. At some point you may want to become aware of Prolog Studio Bugs and Missing Features.

  • If Studio hangs during startup:
    • You should be able to abort startup gracefully by clicking anywhere on the progress bar ( below the bridge picture).
    • On Windows, manually ending the javaw.exe process (via Windows Task Manager) often works, as well.
  • How to report bad behavior, i.e., bugs, hangs, crashes:
    • use the bug report zip feature when possible, send (email) that to
    • if you are unable to use the tools / BUG REPORT feature, please email the .fidji.log file

In any case please check Prolog Studio Bugs and Missing Features.

Installation technicalities

  • Prolog Studio creates a .fidji.prefs Java-style preferences file near the jar file. In that file window positions, favorite font, XSB location etc. are kept. If you need move things around just erase the preferences file (or if you want to preserve it, open it with a text editor and edit the PROLOG line). Make sure you edit while Studio is NOT running, otherwise it will overwrite your changes.
  • You can also launch Studio from an OS shell, to watch Java output directly.
    • java -jar interPrologStudio.jar ...or...
    • ... java -classpath interPrologStudio.jar com.declarativa.fiji.FijiSubprocessEngineWindow Path_to_xsb_executable
  • Studio assumes standard (default) Prolog prompts are on. Changing prompts will likely break communication with it.
  • To diagnose startup problems in new installations, Studio has an ImpatientBugReport object which kicks into action if it detects that the first Prolog engine takes too long to start, drafting a bug report email. If for some reason one wishes to dictate a precise timeout for engine startup, add a preference with the desired limit in milliseconds; the following example will cause Studio to abort the launch and report a bug if it takes longer than sixty seconds:

Oldies Section - previous versions

If somehow you got hit by a buggy bug fix, older versions below:

  • ...