Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!pfkeb From: pfkeb@ebnextk.SLAC.Stanford.EDU (Paul Kunz) Newsgroups: comp.sys.next Subject: Re: NeXT to go with 88K (?) Message-ID: Date: 13 Apr 91 04:33:06 GMT References: <1991Apr10.215125.28932@neon.Stanford.EDU> <2473@fornax.UUCP> <1991Apr12.155212.4476@noose.ecn.purdue.edu> Sender: news@unixhub.SLAC.Stanford.EDU Organization: Stanford Linear Accelerator Center Lines: 15 Nntp-Posting-Host: ebnextk.slac.stanford.edu In-reply-to: songer@orchestra.ecn.purdue.edu's message of 12 Apr 91 15:52:12 GMT NextStep 1.0 .nib files produced on '030 NeXT are readable, editable, and otherwise completely compatible with NextStep 1.0 on an IBM RS/6000 under AIX. Thus, if the byte order is the same (big endian), NextStep compiled on other machines should not have trouble with .nib files. On the other hand, once a .nib file has been edited by NextStep 2.0, its not longer usuable for NextStep 1.0 machine, be it '030, '040, or RS/6000. Such is the price for progress, i.e. the really neat new features in 2.0. .nib files do not contain executable code, as I understand it (someone correct me if I'm wrong), rather they are imbedded in your executable code so that the Application object in each application can read it and reproduce the objects you dragged into your application with the Interface Builder.