Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!ub!boulder!hunt From: hunt@boulder.Colorado.EDU (PUT YOUR NAME HERE) Newsgroups: comp.sys.next Subject: Re: XWindows W11 Release 4 Message-ID: <26590@boulder.Colorado.EDU> Date: 20 Sep 90 03:52:09 GMT References: <2241@opus.cs.mcgill.ca> <92180@srcsip.UUCP> Sender: news@boulder.Colorado.EDU Reply-To: hunt@snoopy.Colorado.EDU (PUT YOUR NAME HERE) Organization: University of Colorado, Boulder Lines: 35 In article <92180@srcsip.UUCP> engstrom@SRC.Honeywell.COM (Eric Engstrom) writes: >> [stuff about how X is being done on the NeXT - deleted...] > > >Sounds good, but I've got a question... > >While I use X (11 rel. 4) on Suns of various denominations (in definite >preference to Sun-Tools), I wonder the use of X on a NeXT. > >Admittedly, X has a large software "base", provides environment >homogeneity among different machine types, and is free & well supported, >but in terms of usability of the environment, I would still rather use >NeXTStep on a NeXT. While I agree the NeXTStep is a nice GUI, what I don't think you understand is the flexibility of X window. The "look" and behavior (window border, gadgets, pop-up window, etc.) are all aspects of the X window _manager_, which can be anything one desires (eg: twm, uwm, motif, openlook, etc.). So I'm sure than someone could make a NeXTStepesque window manager to work pretty much like it does now (although it would most likely be a bit slower). The X window _server_ is what is common to all X window setups -- it's the device that lets you communicate with X window clients (X window applications) and other X window servers. This brings up a very neat concept of X -- the idea that all X terminals are "equivalent" such that you can open a window on any other X terminal (as long as you have permission). This is quite handy when you want to show a window to someone remotely for their pursal. The flexibility and gererality of X makes it a Good Thing. >Eric | --Lee | | Dave Haynie is Bob! | | hunt@spot.colorado.edu ...!ncar!boulder!spot!hunt |