\|// :- /|\\SPIDER is the new SICStus Prolog IDE, based on Eclipse. It is currently in public beta but already quite useful. The latest update was in April, 2019.
See the instructions on how to download and install SPIDER.
SPIDER Getting Started describes how to create a simple Prolog project as well as how to use some of the SPIDER features.
Information about missing and future features is available in the Information for SPIDER Beta Testers.
Code is highlighted based on semantic properties such as singleton variables, definining occurrence …
The editor flags things like calls to undefined predicates, unreachable predicates, incorrect use of predicates and directives, missing declarations … Some warnings comes with quick-fixes, i.e. automatic source-code modifications that fixes the warned about issue.
Problem markers are enabled also for Prolog code that is not open in an editor.
Predicate documentation is parsed on-the-fly and shown when the mouse is hovering over a call. This works for both built-in and user-defined predicates.
Related information, like mode/1 and block/1 directives and various inferred information (determinacy, output arguments) are also shown.
Clicking on a called predicate can bring up its source code.
It is also possible to manually enter the name of any predicate, with completion, and go to its source code.
Clicking on a predicate can bring up a tree of its callers and other references.
A light weight version of this command that just opens the closest caller of the current predicate, is also available.
Predicates are analyzed, on-the-fly, for potential non-determinacy or non-termination.
Predicates are analyzed, on-the-fly, and likely output arguments are shown when hovering over the predicate in a goal.
The predicates in a file are shown in an outline. They can be alphabetically sorted and non-exported predicates can be hidden from the outline.
The debugger shows the names and values of variables.
Backtrace is shown and there are buttons for common debugger actions (Step Over, Step Out, Redo, …).
Source-linked debugging. Works also for code, like the SICStus library, that has no recorded source info.
Line Breakpoints and Spy points can be added by clicking in the left margin of editor.
The ordinary toplevel is still available, with input history and completion. This includes the traditional debugger interface.
You can have multiple SICStus processes running, each in its own toplevel view.
No need to reorganize your code, SPIDER can work with your existing folder structure.
Eclipse provides many features for free, like support for other programming languages, revision control, and much more.