Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!drutx!houxe!hogpc!houti!ariel!vax135!floyd!cmcl2!seismo!hao!hplabs!sri-unix!Bakin@HI-MULTICS.ARPA From: Bakin@HI-MULTICS.ARPA@sri-unix.UUCP Newsgroups: net.works Subject: Xerox Dolphin Message-ID: <834@sri-arpa.UUCP> Date: Wed, 13-Jun-84 13:43:00 EDT Article-I.D.: sri-arpa.834 Posted: Wed Jun 13 13:43:00 1984 Date-Received: Fri, 15-Jun-84 02:18:12 EDT Lines: 33 From: Jerry BakinThe other day, I saw a demo of the dolphin. The demonstrator said that the operating system was multitasking, and that it frequently started up processes. He also mentioned that the mouse was handled by a background process. During the demo, in the top level window (is this the correct term?), I tried to find the 27th number in the fibonacci sequence. This was taking several minutes, (interpreted code) so I moved the mouse to an empty portion of the screen, and asked how I would I create another top level window. To my surprise, I was told I couldn't. There is only one "top level" window at a time. Is this true? Essentially, I wanted to create another process to talk to. Had I just asked the wrong thing? I would have thought I could type: (ADD.PROCESS (read-eval-loop) NAME WINDOW2) Of course, I would have to find out the name of Interlisp's read-eval-loop.... Then, a window would be created for this when it requested I/O, and I'd be in business. Is this not so? Why not? Thanks, Jerry Bakin.