Resource Image vs Image File
Resource Image vs Image File
- Subject: Resource Image vs Image File
- From: Chris Outwin <email@hidden>
- Date: Mon, 14 May 2007 16:58:26 -0500
I am writing an image editing app which seems to require a divergence
from what the docs recommend about placing required resources in
resource files. I've read for days, but haven't found the answer.
Would you please offer some advice based upon these requirements:
The app requires OS 10.4;
There are hundreds of editable images in a 100 MB library. The
application requires the files;
The user can copy an image, edit it and save it individually. The
saved image is immediately displayed in a NSTableView for use in
future sessions;
The app uses Core Data. Images are not store as object data.
Rather, objects reference images by a fileName attribute.
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?
To me, these requirements suggest an image folder which would exist
in /Library/Application Support/(app name) or ~/(etc). Am I wrong?
Can a user save an edited image back to the nib's memory? I can't
find any docs about this?
Thank you,
Chris
_______________________________________________
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