Re: regarding nib files.
Re: regarding nib files.
- Subject: Re: regarding nib files.
- From: Vince DeMarco <email@hidden>
- Date: Fri, 31 Aug 2001 09:49:19 -0700
On Friday, August 31, 2001, at 09:03 am, Enigmarelle Development wrote:
On Friday, August 31, 2001, at 11:12 AM, Vince DeMarco wrote:
When a nib file is loaded all of the
objects are instantiated and connected immediately. Its much better
design to have a separate nib file for each individual window.
What are the advantages of separate nib files, other than faster launch
speeds? I'm working on a single window app, that only has a main window
and an inspector window, plus a couple of controller objects, all in the
mainmenu.nib file - hey, I was a newbie when I started it; now I'm less
of a newbie, but the thing works so I'm reluctant to go tearing it up
again :
}
Would I see a tremendous speed improvement in this type of app by
splitting it up into separate nibs? It seems like better OO design, but
as I said, I finally have a working Cocoa app and I'd like to enjoy the
feeling for awhile!
Its better OO design, firstly.
You will get better launch speeds, only if you arrange to only load up the
nib files when the user requests them, if if the user wants to see the
About panel, you load up the nib and display the panel then.
Another reason is that if there is some bug in IB (heaven forbid, I work
on IB) then we will have only messed up 1 small nib file instead of your
entire application.
Everybody starts off putting there entire application in 1 nib file, now
that you have the app working start splitting it up. I will admit that the
first time i did this it seemed quite difficult as the documentation
describing what to do was kind of limited.
vince