Studio Download and installation
Your download tacitly accepts [Apache LICENSE 2.0] for the files linked to below, except for QUALM (terms at github link below). Use them strictly at your own risk.
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.
But first, you need to have Java installed. Please go to http://www.java.com if you have to.
Installing XSB Prolog
- Download and execute the XSB Prolog installer for your platform
- For Windows, you can simply download and expand this archive (XSB r8664 compiled on April 4, 2016 on Windows 7, 32-bit); please make sure you obtain a XSB directory, with sub directories admin, bin, etc.
- For Mac and other cases (e.g. if you need a 64-bit version for Windows) please go to http://xsb.sourceforge.net/downloads/downloads.html
- Specifically for Mac OS X 10.11.6 (El Capitan), you may use the precompiled version here, the Sep 28, 2016 development version
- Make sure you're able to run xsb from a shell window, e.g. double-click XSB/bin/xsb to get a Prolog console prompt.
Installing Prolog Studio
- Download  into a new (writable) directory; you don't need to expand it.
- Double click interPrologStudio.jar; when asked please indicate where the XSB executable is, for example some\path\XSB\bin\xsb64.bat for Windows (64-bits)
- if you added qualm or LPS, they will load automatically; to uninstall it just delete the respective directory
Installing the QUALM reasoner
- download qualm.zip and expand it into the same directory where you placed interPrologStudio.jar . Studio will load QUALM automatically, displaying "QUALM logic engine loaded" in the listener window.
- NOTE: For this, qualm must be present the first time Studio launches; this not being the case, delete file .ergosuite.prefs and relaunch
- The above is a convenience snapshot of the master branch at github, March 16 2016
- if you need to uninstall it just delete the qualm directory
Installing LPS (Logic-based Production System)
- obtain LPS from its web site and expand it into the same directory where you placed interPrologStudio.jar . Make sure LPS has subdirectories 'examples', etc. (this check is necessary because depending on how you extract the zip it may create an intermediate LPS directory ;-) ).
- Studio will load LPS automatically, displaying "LPS engine loaded" in the listener window.
- NOTE: For this, the LPS subdirectory must be present the first time Studio launches; this not being the case, delete file .ergosuite.prefs and relaunch
- if you need to uninstall it just delete the LPS directory
If things go bad
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 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, and email the zip file to firstname.lastname@example.org
- 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.
Or send us an email, we'll try to help.
- Prolog Studio creates a .ergosuite.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 -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:
Main changes since the last version
In the latest version downloadable above (September 11, 2016):
- LPS Support
- Experimental alternative "papers syntax", file extension .lpsp; see Help / Open LPS Example
- Timelines visualised with the system browser; use File/Load in a LPS editor window
- Minimal Java API, class LPSEngine
- Let the editor open .pl and .p files
- Misc bug fixes
If somehow you got hit by a buggy bug fix, older versions downloadable below:
- April 4, 2016 interPrologStudio.jar interPrologStudio.jar
- QUALM support
- Automatic loading at startup (if QUALM is present)
- Help / Open QUALM Examples menu
- Editor (for files with extension .ab):
- File / Load redefined to Load QUALM
- warnings: bad abducibles declared; undefined predicate warnings depend on abducibles
- Call tree and call graph based on QUALM source code rules (and not on the transformed Prolog rules)
- LPS support
- Automatic loading at startup (if LPS is present)
- Help / Open LPS Examples menu
- Command history in listener and query windows persists between sessions (in file .PrologStudioHistory.txt)
- Smarter listener scrolling
- fjSubgoalDependencyGraph shows the SDG, cf. XSB Manual Vol I, 10.3
- Editor "Back" command in Edit menu, and warnings of meta calls
- Underlying Java bridge now with preliminary support for YAP and SWI Prolog too (via YAPSubprocessEngine and SWISubprocessEngine resp.; documentation TBD)
- Misc bug fixes
- QUALM support
- June 15, 2015 interPrologStudio.jar
- global error/warning strip lines in editor windows
- editor window titles get a * when needing saving
- Prolog output appears in a different color in the listener
- Copy/paste/undo in listener input field and query window
- Misc bug fixes
- January 15, 2015 interPrologStudio.jar
- Includes latest (today's) version of Java bridge
- Editor, project, warnings and error and tabled data windows that were VISIBLE at the end of a session will now automatically REOPEN; but only if there is a preference com.declarativa.fiji.FijiSubprocessEngineWindow.reopenWindows=true (default false)
- Compatible with latest (dev) XSB Prolog as of today
- Some bug fixes* interPrologStudio.jar (r486, Oct 28 2014)
- First public version
(source code links will be made available on request)