The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Brad Spencer <>
To: "G. Branden Robinson" <>
Subject: [TUHS] Re: OLIT, MoOLIT, and NeWS (was: X11 Conservancy Project)
Date: Sun, 25 Dec 2022 16:03:11 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20221225205151.x3kflt7qrjc3b7i4@illithid> (

"G. Branden Robinson" <> writes:


> And MoOLIT was, apparently, some kind of shim--whether it supplemented
> OLIT or replaced it, I am not sure--that, like XForms and Java's AWT,
> allowed you to to write a "look-and-feel-neutral" application.


Motif on OLIT, if I remember that correctly.  Sort of a Motif look and
feel but without the need to purchase a license for Motif which you had
to do at the time (that is, in order to even RUN a motif linked
application, you needed the shared libraries which you could pretty much
only get by purchasing a license..  there was probably other ways, and
it has been a LONG time ago).  Our group at AT&T used it to keep from
having to have the customer buy anything additional for a release but
who also wanted "Motif".  I don't honestly remember if you coded in OLIT
or Motif, but probably OLIT, but the end result was something that sort
of looked like Motif in the end.

Brad Spencer - - KC8VKS -

  reply	other threads:[~2022-12-25 21:05 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   ` Brad Spencer [this message]
2022-12-25 21:38   ` [TUHS] " josh
2022-12-25 21:47     ` Ron Natalie
2022-12-26  6:26     ` arnold
2022-12-26 19:37       ` Jon Steinhart
2022-12-26  4:18   ` Warner Losh
2022-12-26  9:59 ` [TUHS] Re: X11 Conservancy Project Lars Brinkhoff

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:

* 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).