Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!think!snorkelwacker!bloom-beacon!GEO785.GCN.UOKNOR.EDU!jay
From: jay@GEO785.GCN.UOKNOR.EDU
Newsgroups: comp.windows.x
Subject: MOTIF
Message-ID: <9001021832.AA13197@expo.lcs.mit.edu>
Date: 15 Dec 89 13:47:00 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 28

This is a reply to Jon about the MOTIF vs. DECWindows problem.

After talking to several DECies about super-portability for X-applications
(which was the initial target for X), I was informed that to be upwardly 
compatible, it would be a good idea to get MOTIF from OSF.   I am sure
(which means I am probably using common sense) that the MOTIF toolkit
is different than the DECWindows toolkit.  In other words you/I/we folks that 
want to have portable X code are going to have to lock in on a toolkit and
eat it if something better comes along.  I hope that DEC figures out how many
people that they are going to SLIME if they don't stay real close to OSF's
MOTIF.  The thing that makes me want to flame is that DEC used PART of the 
Xt toolkit to make DECWindows (on VMS and ULTRIX), took some (as in not all) of
the include files from the consortium hacked on them a little bit (took out 
usefull things like Label.h...), and turned their version out before they 
should have. (I bet I have pissed some folks off by now.)  I am about to 
undertake a rather large 100k+ line project and have to depend on things like
portability (it has to run on a CRAY/SUN/VAX/STELLAR/ALLIANT).  (I am in 
trouble right.)  Anyway ***Flame off***  and watch out jon.

Anyway if you want to talk to me call me.  If you want to flame at me 
(personally) over mail CAST OFF.  

					Later,
					Jay A. Davis
					Work:  (405) - 325 - 5540

Guess what:  These are MY views not the University of Oklahomas views.
They don't even know I sent the letter, so there!