Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!usc!ginosko!uunet!kddlab!titcca!sragwa!wsgw!socslgw!csl.sony.co.jp
From: kono@csl.sony.co.jp (Shinji Kono)
Newsgroups: comp.lang.prolog
Subject: Re: Suntools and Sicstus/Quintus Prolog
Message-ID: <10688@socslgw.csl.sony.co.jp>
Date: 10 Aug 89 04:23:22 GMT
References: <185@cui.unige.ch>
Sender: kono@csl.sony.co.jp
Reply-To: kono@csl.sony.co.jp
Organization: Sony Computer Science Laboratories, Inc.
Lines: 24

In article <185@cui.unige.ch>  , afzal@cui.unige.ch (Afzal Ballim)writes 
> Hi, does anyone have code (or directions) for setting up an interface
> between Sicstus/Quintus Prolog and Suntools? 

Quintus Prolog has a sample window library for Suntools. It uses
foregin libarary interface for C. It also works on sicstus prolog.

Generally it is not difficult to write simple interface to Window or
Socket in SICStus/Quintus. I wrote one general socket interface and a
window interface for GMW (Tateishi-Omron Japan's window system, nobody
knows :-).  One advantage of using prolog is this: you can use repeat
fail for dragging.
	?- get_newevent(X), drag_something(X), check_event(X).
	drag_something(X) :- write_something(X).
	drag_something(X) :- get_newevent(X1), erase_something(X),
		drag_something(X1).
This is very slow in interpreter, but reasonably fast in compiler. 

But these make Prolog really BIG, and using low window interface is
real pain. Real problem is high level interface design for various
window system.
--------
Shinji Kono 
$@2OLn??<#(J Sony Computer Science Laboratory, Inc.: kono@csl.sony.co.jp