The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jonathan Gray <jsg@jsg.id.au>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Earliest UNIX Workstations?
Date: Mon, 30 Jan 2023 16:23:53 +1100	[thread overview]
Message-ID: <Y9dUaQf+btXgTttl@largo.jsg.id.au> (raw)
In-Reply-To: <B5198799-9629-4CB4-9EE5-39FABEFF35D7@planet.nl>

On Mon, Jan 30, 2023 at 12:20:52AM +0100, Paul Ruizendaal via TUHS wrote:
> 
> 3. Next is the 1989 NeWS book that has a nice overview and history of windowing systems in its chapter 3:
> 
> http://bitsavers.trailing-edge.com/pdf/sun/NeWS/The_NeWS_Book_1989.pdf
> 
> Both the UK conference and the NeWS book mention a Unix kernel-based windowing system done at MIT in 1981 or 1982, “NU" or “NUnix”, by Jack Test. That one had not been mentioned before here and may have been the first graphical windowing work on Unix, preceding the Blit. Who remembers this one?

mentioned in ;login: Volume 7 Number 4, September 1982
https://archive.org/details/login_september-1982/page/24/mode/2up
Notes on the Boston USENIX and /usr/group Joint Meeting July 1982

"NUnix Window System Description

Jack A. Test
Laboratory for Computer Science, Massachusetts Institute of Technology,
Room 414, 545 Technology Square, Cambridge, Mass 02139

The NUnix Window System is a set of software that provides a user a
basic window management mechanism on a high resolution display.
It was developed for use with the MIT Real Time Systems Group NU
Personal Computer, a 68000-based machine which uses a 820x1024 point
raster-scan display, keyboard, and mouse for the user interface.
The NU machines are being used for developing a multi-font editing
system and drawing facility, in several circuit design projects,
and in the development of new operating system concepts.

The user may create multiple overlapping rectangular windows on the
display. Each is associated with an independent UNIX teletype device
and a display device. A window may have up to eight independent and
changeable font maps. The windows are controlled with ioctl calls
and special signals. These allow such actions as creating a new
window, drawing on it, selecting or changing the fonts associated
with it, reading the state of the mouse, obtaining and/or changing
the state of the window, etc. Each window belongs to a process-group
to which a signal is sent whenever there is a change to the attributes
of the window. There is a window-manager program which makes use
of the mouse device to allow the user to select functions from a set of
displayed menus. The user also has access to the display bitmap and a
special graphics routine library.

The NUnix Window System is implemented in a set of device-driver
routines in the UNIX V7 kernel. Most of the window driver code is
machine independent with the exception of two low-level routines
for driving the raster display and keyboard devices respectively.
The NUnix Window System provides a basic window management mechanism
that: (1) is transparent to the vast majority of user programs, (2)
provides a clean user interface without the addition of any new
system calls, and (3) allows user processes to manage their windows
independently and with minimal kernel-imposed limitations.

The code for the NUnix Window System is available from MIT if you
have a UNIX V7 license. The speaker has submitted a paper for the
Conference Proceedings."

goes on to briefly cover:

Design of an Intelligent Bitmap Terminal
Rich Fortier and Tony Lake
Bolt Beranek and Newman Inc., 10 Moulton St., Cambridge, Mass 02238

The SUN Workstation
Andreas Bechtolsheim
Sun Microsystems, 2310 Walsh Ave., Sania Clara, CA 95051

Merging Bitmap Graphics and UNIX
Rob Pike
Bell Labs 2C-521, Murray Hill, NJ 07974

a different writeup of these is in:

https://www.tuhs.org/Archive/Documentation/AUUGN/AUUGN-V04.5.pdf
September 1982, Vol IV No V
July Usenix Abstracts

  parent reply	other threads:[~2023-01-30  5:24 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29 23:20 Paul Ruizendaal via TUHS
2023-01-30  0:25 ` Jonathan Gray
2023-01-30  5:23 ` Jonathan Gray [this message]
2023-01-30  8:45   ` Paul Ruizendaal
2023-01-30  9:22   ` Jonathan Gray
2023-01-31 11:35   ` Paul Ruizendaal
2023-01-31 23:29   ` Chris Hanson
2023-01-30 13:00 ` Lars Brinkhoff
2023-02-06  7:01 ` Jonathan Gray
2023-02-06  8:39   ` Jonathan Gray
2023-02-06 10:03     ` [TUHS] window systems (was Re: Earliest UNIX Workstations?) Jonathan Gray
  -- strict thread matches above, loose matches on Subject: below --
2023-01-26 15:58 [TUHS] Earliest UNIX Workstations? Paul Ruizendaal
2023-01-26 16:04 ` [TUHS] " Larry McVoy
2023-01-26 16:37   ` emanuel stiebler
2023-01-26 16:51     ` segaloco via TUHS
2023-01-26 16:29 ` Clem Cole
2023-01-26 22:17   ` Paul Ruizendaal
2023-01-26 22:45     ` Bakul Shah
2023-01-27  0:19       ` Paul Ruizendaal
2023-01-27 17:16         ` Paul Ruizendaal via TUHS
2023-01-27 17:36           ` Warner Losh
2023-01-27 17:37             ` Warner Losh
2023-01-27 17:45               ` Rich Salz
2023-01-27 17:54                 ` Warner Losh
2023-01-28  9:14                   ` Lars Brinkhoff
2023-01-28 11:05                     ` Paul Ruizendaal
2023-01-28 15:38                       ` Warner Losh
2023-01-28 18:50                       ` Lars Brinkhoff
2023-01-29  6:48                     ` Lars Brinkhoff
2023-01-29 20:39                       ` Paul Ruizendaal
2023-01-27 17:43           ` josh
2023-01-26 16:51 ` Warner Losh
2023-01-26 18:15   ` Lars Brinkhoff
2023-01-26 19:39     ` Bakul Shah
2023-01-27 10:59     ` Lars Brinkhoff
2023-01-26 18:14 ` Jon Steinhart
2023-01-26 20:44 ` Rob Pike
2023-01-26 13:15 Paul Ruizendaal via TUHS
2023-01-26  0:31 [TUHS] " Joseph Holsten
2023-01-26  0:51 ` [TUHS] " segaloco via TUHS
2023-01-26  1:06   ` Luther Johnson
2023-01-26  1:15     ` Jon Steinhart
2023-01-26  1:01 ` Larry Stewart
2023-01-26 13:25   ` Marc Donner
2023-01-26 13:58     ` arnold
2023-01-31  2:03   ` Mary Ann Horton
2023-01-31 17:43     ` Marc Donner
2023-01-26  1:12 ` Tom Lyon
2023-01-26  1:47 ` Chris Hanson
2023-01-26  7:20   ` John Cowan
2023-01-26  7:33     ` Dave Horsfall
     [not found]     ` <CAD2gp_QtUPmd78yAixvKK1wzPX67HKZXzU5cJnVUbcWtMounGQ@mail.g mail.com>
2023-01-26 16:35       ` John Foust via TUHS
2023-01-26 17:58     ` Jon Forrest
2023-01-26 18:04     ` Jon Steinhart
2023-01-26  9:52 ` emanuel stiebler
2023-01-26  9:58   ` Rob Pike
2023-01-26 10:09   ` Jaap Akkerhuis via TUHS
2023-01-26 15:14 ` Clem Cole

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y9dUaQf+btXgTttl@largo.jsg.id.au \
    --to=jsg@jsg.id.au \
    --cc=pnr@planet.nl \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).