Re: Resource Image vs Image File
Re: Resource Image vs Image File
- Subject: Re: Resource Image vs Image File
- From: Thomas Engelmeier <email@hidden>
- Date: Wed, 16 May 2007 10:03:49 +0200
Am 14.05.2007 um 23:58 schrieb Chris Outwin:
Isn't it wasteful to have the nib load the entire 100 MB image
library when only some of the images will be edited in a session?
"the nib" will not "load" all images, and NSBundle (the class
instance managing scattered Cocoa resource files) won't, either.
(Maybe the names get cached, though). NSBundle will provide an way to
access the resource files, think of it as a specialized NSFileManager
that does a two-way lookup (first for a localized version, then for a
default version) in the specified folder with quite some name /
extension flexibility.
It is completely different from the Carbon resource manager that will
memory-map the complete resource fork and keep quite a bunch always
accessible.
Can a user save an edited image back to the nib's memory? I can't
find any docs about this?
Generally, no. Don't consider your app bundle writable, even though
for you it probably is (otherwise you couldn't create it).
Regards,
Tom_E
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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