On Jul 25, 2010, at 11:41 PM, Amy Gibbs <h...@willowtreecrafts.co.uk> wrote:
> I'm working on a core data app that has an entity called Product. I'd like to > have an image attribute for it but I'm expecting the app to have thousands of > products stored over time so storing the images in the app will bloat it out > and slow it down. Nitpick: "in the app" implies the images are stored inside your app bundle's Resources folder. You probably meant "in the persistent store." > > > What I'd like to do is have an imagewell on the interface where I could drop > an image from the finder and it would copy the image file to a set > destination and save the filename to the store so it can just be referenced. > > In another part of the interface I'd like a collection view that displayed > all the product images for a given relationship. > > Does this seem like the right approach or am I completely wrong? This is one recommended approach in the Core Data documentation for things like large image attachments. So you're on the right track. > > I'm a beginner so I apologise if this is a stupid question, if you could > point me in the right direction I'd appreciate it. Core Data is not a beginner technology; I would highly recommend starting smaller and working your way up. --Kyle Sluder_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
