From: Larry McVoy <lm@mcvoy.com>
To: Michael Parson <mparson@bl.org>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Atari System V media and books?
Date: Wed, 5 Feb 2020 19:54:57 -0800 [thread overview]
Message-ID: <20200206035457.GF21264@mcvoy.com> (raw)
In-Reply-To: <alpine.NEB.2.21.2002052143370.676@neener.bl.org>
On Wed, Feb 05, 2020 at 09:44:02PM -0600, Michael Parson wrote:
> On Wed, 5 Feb 2020, Chris Hanson wrote:
> >On Jan 18, 2020, at 3:19 PM, Michael Parson <mparson@bl.org> wrote:
> >
> >>Speaking of old versions of Motif, are the sources for the
> >>pre-OpenMotif bits available anywhere? Even if under lock and key
> >>for now, I'd be happy knowing they'd been preserved for potential
> >>future availability.
> >
> >There are Motif 1.1 sources on Bitsavers (or your favorite mirror)
> >at <http://www.bitsavers.org/bits/OSF/OSF_Motif_Src_1.1.X/
> ><http://www.bitsavers.org/bits/OSF/OSF_Motif_Src_1.1.X/>>.
>
> Thank you!
Part of me is wondering why anyone cares about Motif. My memory of that
is that Xview was better and the Athena widgets were better. Athena was
ugly but it worked, Xview, the X11 version of Sunview, was fantastic to
program in, the argv was a set of 2 tuples, thing and value. And it
looked better. I've written Xview apps and other than the Tk part of
Tcl/Tk, it was the most pleasant GUI API I have used. For the record,
the Tk part of Tcl/Tk is still, decades later, the best GUI interface
I've ever seen. John got that right.
So no offense intended, what about Motif is likeable?
next prev parent reply other threads:[~2020-02-06 3:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 22:48 Chris Hanson
2020-01-18 23:19 ` Michael Parson
2020-02-05 23:29 ` Chris Hanson
2020-02-06 3:44 ` Michael Parson
2020-02-06 3:54 ` Larry McVoy [this message]
2020-02-06 15:35 ` Chet Ramey
2020-02-06 15:50 ` Michael Parson
2020-02-06 17:58 ` Arno Griffioen
2020-02-06 23:15 ` Michael Parson
2020-02-07 11:53 ` Arno Griffioen
2020-02-06 4:02 ` Henry Bent
2020-02-06 5:05 ` Clem Cole
2020-01-18 23:27 ` Arthur Krewat
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=20200206035457.GF21264@mcvoy.com \
--to=lm@mcvoy.com \
--cc=mparson@bl.org \
--cc=tuhs@minnie.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).