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:21:08 -0400
On 7/25/07, John Stiles <email@hidden> wrote:
For example, imagine your laptop user goes to visit some rarely-used window
five minutes after the app has started up—there will be a huge delay while the
hard drive spins back up so it can read 2K of NIB data off the disk.
An excellent argument. It comes back, then, to whether a first load
of a nib is cached like [NSImage imageNamed:@"foo"] ... if that's the
case, you still have a clear advantage when in the
many-instances-of-a-complicated-editor situation. Otherwise, perhaps
loading your very small preferences window from a separate nib *is* a
bit overboard ...
The prefs windows in my apps tend to be ... extensive. :-D I'm a
big fan of configurability and I separate things out into separate
panels, have a rather complicated controller (I use the
select-the-toolbar-item-and-do-an-animated-window-resize prettiness)
and icons / custom controls that don't show up anywhere else but in
prefs. This tends to cause a lot of work, so it's a good candidate to
leave behind at launch time.
Well, except for laptop users, anyway. :-)
--
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