Objective-C Issues

interface-builder

People ( From: lines )
 shirley@gothamcity.jsc.nasa.gov (Bill Shirley [CSC])
Subjects ( 1 mails )
 read/write  - NIB
Document
Date: Thu, 17 Sep 92 10:46:06 CDT
From: shirley@gothamcity.jsc.nasa.gov (Bill Shirley [CSC])
To: gnu-objc@prep.ai.mit.edu
Subject: read/write  - NIB

|> >|>                              --the object can be arbitrarily complex,
|> >|> e.g., the filer will handle vanilla C instance variables,
|> >|> chase object ids, yet avoid duplicating objects to which there
|> >|> is more than one pointer.  A more flexible design might allow one
|> >|> to store/access many objects per file.
|> >
|> >like NIB files.
|> 
|> Sorry, what's a NIB file?

whoops, sorry, I might as well share this with all just for knowledge's 
sake.

NeXT's Interface Builder (which some tout and others scorn)
creates NIB files, which are loaded in by the Application
Object (usually) before an [App run] message is sent.

It is basically an archive of all the instanciated objects that
were created in the Interface Builder.  Thus is contains "more
than one object" which the previous discussion was about.

Multiple NIB files are often used for parts of the program that
may or (usually) may not be brought into play.  Such as a window
with detailed help features or an "info box".

-Bill

Statistics
 filename:           interface-builder
 number of mails:    1
 number of writers:  1
 line count:         32
 word count:         190
 character count:    1162

created by Helge Hess ( helge@mdlink.de )
MDlink online service center ( www.mdlink.de )