Re: Guidelines for NIB usage
Re: Guidelines for NIB usage
- Subject: Re: Guidelines for NIB usage
- From: "I. Savant" <email@hidden>
- Date: Wed, 25 Jul 2007 14:01:10 -0400
On 7/25/07, Kevin Hoffman <email@hidden> wrote:
With .NET you have to manually instantiate each window, but your entire
Assembly is loaded into memory at app startup time anyway so deferring
the instantiation isn't really gaining you much.
An important thing to keep in mind, yes. The more UI your app has to
create at launch time, the longer the launch time will take.
Of course there's a trade-off (isn't there always?): In the
Preferences example I gave previously, the first time the user *does*
open the preferences window (causing the NIB to load) during that
session, there will be more of a delay than each subsequent time
during that session. For huge UI chunks, this may or may not be
acceptable.
In the case of many complicated "editors", the load-time
requirements change ... I have no idea off the top of my head
(enlightenment, anyone?) if any optimization / caching is done for
NIBs, but if not, suddenly the idea of creating a new complex editor
window by loading it from a nib for each object you want to edit
requires more serious deliberation.
I'd *love* to hear from the community about that one, though. I
honestly don't know for sure but don't care enough at the moment to
look it up myself. :-D
--
I.S.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden