From: Rich Morin <email@example.com>
To: TUHS main list <firstname.lastname@example.org>
Subject: [TUHS] Re: Nice video with Brian Kernighan
Date: Sun, 21 Aug 2022 13:07:42 -0700 [thread overview]
Message-ID: <48947943-90FA-43DA-A7FD-4B75BE9549C7@cfcl.com> (raw)
> On Aug 21, 2022, at 08:09, John Cowan <email@example.com> wrote:
> On Sat, Aug 20, 2022 at 2:26 PM Rich Morin <firstname.lastname@example.org> wrote:
> - used AWK to convert the data for use with my SunCore interpreter
> What is this SunCore of which you speak? Dr. Google reports too many confounds. ...
I was able to find some web mentions of the relevant SunCore. I've put a set of links below, which others may well be able to improve upon. Anyway, the SunCore Graphics Package shipped with early versions of SunOS. It was a set of C libraries which allowed programs to draw on the bitmapped display. My interpreter read simple text commands (eg, "fn_name arg_1 ..."), parsed them, and made the specified library calls.
P.S. For the curious...
The dendrogram plotting software, which ran on U of MD's IBM and Univac mainframes, generated line printer plot files. These used characters such as dashes and vertical bars to draw the dendrogram "trees". So, Vicki's code needed to scan the files, extract the shape of each tree, and generate plotting commands for my interpreter.
The production process for that part of Vicki's thesis was roughly as follows:
- hand-code data files in a common, human-friendly format (vi)
- convert into formats for the IBM and Univac software (AWK)
- upload and process the files, then download the results
- analyze the line printer plot files of dendrograms (AWK)
- generate commands for the SunCore interpreter (AWK)
- run the interpreter, generating diagrams on the display
- dump bitmap images of the displayed diagrams
- print the images, using a dot-matrix printer
The text portion of the thesis was generated using a different tool chain:
- create and/or edit the thesis text (vi)
- format the text for printing (nroff)
- print on an IBM I/O selectric (Datel 30)
Printing on the Datel 30 was complicated by several factors. It wanted BCDIC correspondence code, rather than ASCII. Also, it needed null characters to provide enough time for various activities (eg, print ball rotation, carriage returns, line feeds). And, given that paper feeding was a manual process, we needed a way to initiate printing of a new page, reprint botched pages, etc. So, I wrote a small utility program that handled all of this.
next prev parent reply other threads:[~2022-08-21 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 15:48 Douglas McIlroy
2022-08-20 16:17 ` Clem Cole
2022-08-20 18:24 ` Rich Morin
2022-08-21 15:09 ` John Cowan
2022-08-21 15:41 ` Clem Cole
2022-08-22 2:49 ` John Cowan
2022-08-21 20:07 ` Rich Morin [this message]
2022-08-21 9:36 ` Mohamed Akram
-- strict thread matches above, loose matches on Subject: below --
2022-08-18 10:01 [TUHS] " Arnold Robbins
2022-08-18 21:58 ` [TUHS] " Clem Cole
2022-08-18 22:48 ` Pete Wright via TUHS
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).