Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!caen!hellgate.utah.edu!csn!datran2!smb From: smb@data.com (Steven M. Boker) Newsgroups: comp.sys.next Subject: Re: Macro Language and IB code (was: Re: Preview / YAP / Printing / Digitial Librarian) Message-ID: <1991Mar20.165430.2364@data.com> Date: 20 Mar 91 16:54:30 GMT References: <68871@brunix.UUCP> <69158@brunix.UUCP> Organization: Data Transforms, Inc. Lines: 20 In article <69158@brunix.UUCP> rca@cs.brown.edu (Ronald C.F. Antony) writes: [many good comments deleted] >As good and as practical as .nib files are, there is a need to have >some textual equivalent to them. I agree completely here. Documentation of my IB work is a manual task at this point. It shouldn't be. I think Ronald has pointed to one of the few weak spots in the IB development process. Those at NeXT who are reading this should take note. Implementing Ronalds idea would be a boon to the more-than-casual developer. Steve -- #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====# # Steve Boker # En Vino Kaos # # smb@data.com # En Kaos Veritas # #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====#