Re: [OT?] Nib files balloon app size
Re: [OT?] Nib files balloon app size
- Subject: Re: [OT?] Nib files balloon app size
- From: Yuhui <email@hidden>
- Date: Fri, 11 Apr 2003 20:07:26 -0500
Thanks for the tip!
On the other hand, this seems like a gross oversight in the development
tools. Shouldn't PB remove those files when building a Deployment
product? I can understand if it leaves them in during Development, but
not for Deployment.
Yuhui
On Friday, April 11, 2003, at 07:35 PM, Amul Goswamy wrote:
Before you undo the optimizations to your app, you could try stripping
the nibs in your application package.
You can remove the classes.nib and the info.nib files from the nib
packages of you production nibs. You must leave your development nibs
intact or you will have difficulty editing them. Stripping these
files from your application package will reduce the application size
and will also prevent users of your app from altering the user
interface.
Amul Goswamy
Interface Builder QA
Apple
On Friday, April 11, 2003, at 05:06 PM, Yuhui wrote:
Recently, I started moving my app's individual windows to separate
Nibs, as suggested by Apple's documentation to reduce resource usage
at runtime. However, I've found that the more Nibs I create, the
larger my app gets. E.g. if I take a window from one Nib and put it
in a new Nib, the final app size becomes larger with the 2 Nibs than
with just one Nib. This has made me reconsider creating separate Nibs
for each window. I want to keep my app size down, primarily because a
smaller app means faster download times.
So I have 2 questions:
1. Is it reasonable for me to choose small app size over optimized
resource loading?
2. Why do more Nibs mean larger app size, when they have the same
number of windows/panels between them?
Thanks
Yuhui
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.