From: Jon Steinhart <email@example.com>
Subject: [TUHS] Re: OLIT, MoOLIT, and NeWS (was: X11 Conservancy Project)
Date: Mon, 26 Dec 2022 11:37:12 -0800 [thread overview]
Message-ID: <202212261937.2BQJbD53508609@darkstar.fourwinds.com> (raw)
> josh <firstname.lastname@example.org> wrote:
> > > Ranging a bit farther afield, I wonder similarly about Sun's NeWS, which
> > > I never saw in the flesh.
> > Branden,
> > You may find this fellow’s archaeological dig on NeWS and PostScript
> > interesting: https://twitter.com/rsnous/status/788053163857379328
> The link there gets to https://github.com/IanDarwin/OpenLookCDROM
> which has NeWS and a bunch of other stuff. Possibly worth copying
> into the TUHS archive.
Ah, 'tis the season for old past follies.
Somewhere I have an old Christmas card that Dave Lavalle helped me make
for James Gosling using NeWS and taking advantage of the color printer
that had somehow been justified. I'll scan it when I find it. The
text of it was "Merry X-Mess and a Happy NeWS Year".
Related to all this, the original PostScript source has recently been
My major beef with NeWS was that it perpetuated the awful X input model
where everything had to be rectangles. NeWS greatly improved graphics
but not input. Being an ancient graphics person, I thought that it should
have followed the "pick identifier" model from the traditional (light pen)
vector graphics days where identifiers could be associated with objects
that were reported when they were selected. NeWS could have done amazing
things by adding a pick identifier to the graphics context, and in the
PostScript way having that be polymorphic. Would have greatly simplified
a lot of user interaction programming to be able to associate a function
with an object, and to not have to have a bazillion separate input
rectangle for each part of a window border and so on.
next prev parent reply other threads:[~2022-12-26 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-25 18:15 [TUHS] X11 Conservancy Project Michelangelo De Simone
2022-12-25 19:16 ` [TUHS] " segaloco via TUHS
2022-12-25 19:57 ` Michael Kjörling
2022-12-25 20:51 ` [TUHS] OLIT, MoOLIT, and NeWS (was: X11 Conservancy Project) G. Branden Robinson
2022-12-25 21:03 ` [TUHS] " Brad Spencer
2022-12-25 21:38 ` josh
2022-12-25 21:47 ` Ron Natalie
2022-12-26 6:26 ` arnold
2022-12-26 19:37 ` Jon Steinhart [this message]
2022-12-26 4:18 ` Warner Losh
2022-12-26 9:59 ` [TUHS] Re: X11 Conservancy Project Lars Brinkhoff
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).