Please use our mailing list. (You need to subscribe first.)

There are no fixed requirements regarding format or included information. Just describe your problem. It never hurts, though, to include the following:

• A complete log file is helpful in 80% of all cases:
  • See Window > Preferences > PDT Preferences
  • Set the Debug Level to “Debug”.
  • Make sure you have write permissions on the log file.
  • Restart Eclipse and try to reproduce the problem.
  • Shutdown Eclipse and send us the log file. Off-list, if you prefer.
• What version of the PDT, Eclipse and SWI-Prolog do you run?
• Which platform do you use?
• Can you start SWI-Prolog from the command line? Does XPCE work? (E.g. can you use the graphical help system or debugger?)

Download the installation file and unzip it in your Eclipse directory. Make sure you've read the notes on compatibility of PDT versions and Eclipse versions on our download page.

The Prolog Interface is the subsystem that enables Java code to interact with SWI-Prolog. It is included in the PDT package. Because it can also be used independently of the PDT or Eclipse we provide it as a separate download.

We deploy two kinds of releases: milestones and service releases. Simply put, milestones contain new functionality, successively approaching the upcoming major version (like 0.1, 0.2, etc). Service releases (0.1.1, 0.1.2, etc) fix problems in the current major version, but the general contract is that they do not change functionality or public APIs in any way.

In general you should always try the latest version available. Very often, even when a version labeled “milestone” its overall usability will be better than that of older versions labeled as “service” or “stabel” versions. There might be situations however, where some other plugin you use requires API features, that have become obsolete in the latest release. If in doubt, and if not told otherwise, just take the latest version.

Select the menu item “Window –> Customize Perspective…”, then select the “Commands” tab. Scroll down the “Available commands” column until you see the item “org.cs3.pl.actionSet1”. Make sure it is checked.

You must

• either activate the "Prolog project nature"In the Package Explorer, right click on the Project that contains Prolog code and check the “Configure > Add Prolog project nature” item in the context menu.
• or consult your files To consult the file whose editor window is currently selected / active / having focus press F9 or klick the “PRolog > (re)consult” menu item (when working without Prolog project nature).

The Prolog Console is an Eclipse view. It can be opened via Window→Show View→Other…

You do not need to enter the '?-' used in some Prolog systems to start a query. Simply type your query in the “input pane” (the lower pane of the Prolog Console View). Terminate it with a dot ('.') and <return>. The results will be displayed in the the “output pane” (the upper pane of the Prolog Console View).

Simply type ';' in the lower pane (the input pane) of the Prolog Console View. The next result will be displayed in the output pane. You can repeat this until the output pane displays 'No', which means that no more results are available for your query.

You can use the <up> and <down> keys to scroll up and down through the command history. See the PDT keyboard shortcuts.

All source code is deployed together with the normal binaries. If you have installed the PDT plugins, you already have the source code. Most of it is included in the jar files, which you can easily unzip using tools as WinZIP.

After some ongoing cleanup and documentation we will make our code available on GIThub. In the meantime, if you are interested in contributing, please contact us. Sorry for the inconvenience.

If you are experiencing any complications while trying to get PDT to work, please refer to the Platform Notes.