Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!dino!ux1.cso.uiuc.edu!milo.mcs.anl.gov!atlantis.ees.anl.gov!korp From: korp@atlantis.ees.anl.gov (Peter Korp) Newsgroups: comp.windows.open-look Subject: Re: What's the diff between xview and xt+? Message-ID: <1990Nov14.170501.2667@mcs.anl.gov> Date: 14 Nov 90 17:05:01 GMT References: <102130@cc.utah.edu> <1990Nov14.145853.12678@cbnewsm.att.com> Sender: news@mcs.anl.gov Organization: Advanced Computer Application Center, Argonne National Laboratory Lines: 36 Nntp-Posting-Host: atlantis.ees.anl.gov >In article <102130@cc.utah.edu>, EYRING@cc.utah.edu writes: >> What is the difference between xview and xt+? Thought that Motif >> was the xt intrinsics, but what is the xt+ toolkit that is provided >> with OpenLook? Does dev guide produce xview or xt+ code? > >XView is an X11 toolkit that is NOT based on the X Consortium standard Xt. > Oh come on now.... XView is an X11 toolkit based on Xlib, which is just as "standard" as Xt. If Xlib changes, Xt code will break too. I happen to find code written in the "SunView" API much cleaner than code written using any Xt based toolkit. Sun uses C varargs quite a bit in XView, a feature only recently introduced in the R4 Xt. This "standards" thing has gotten a bit out of hand. [Xt+ and Motif discussions deleted] >Having the various options and implementations seems to have done more >to confuse people than to help them by providing flexibility, but maybe >the confusions will be only temporary and the market will benefit from >having the options. I think that was the original intent, anyway :-) Yes it was, quickly porting 2000+ SunView apps was an important consideration for Sun in the design of XView. If you were starting from scratch and like to belive all this "standard" stuff OLIT (Xt+) is for you. >-- >Michael L. Siemon "O stand, stand at the window, >m.siemon@ATT.COM As the tears scald and start; >...!att!sfsup!mls You shall love your crooked neighbor >standard disclaimer With your crooked heart." Peter