Question regarding master data and camera

Question

So, I'm working on an application that uses kernel data to store attributes of objects that the user can set. First of all, I focused on the first part, which set everything up on the main side of the data, and now I am ready to move on to the next part concerning the camera. I want to be able to add a city or other geographical location (this is an object), and then be able to take pictures in my application that would accordingly save these images (or attributes) under the object. For example, when I click New York on my uitableview, I would be able to view any number of photos that I took in New York. When I click on Florida, I can see any photos I took in Florida. So my question is, is this possible or not? Sorry, that was a vague question. If I could take pictures from my application, could I also save them there? And make a list of them in my application? I suppose I foresee a separate data-esque look that looks uitableview with a place object that lets you control the photos so that they are directly visible, like a slide show, where I could see all the pictures I took in this location. Is it possible or will they be saved in the default location of the image in the picture app? Apparently there would be some kind of memory limitations? Or can I remove multimedia from the memory (8 GB, 16 GB, etc.)? I think that my questions are not about specific code examples, how many are intended for directed purposes. If anyone has any ideas / ideas to help me, we will be very grateful. Thanks!

Answer 1

The design you describe is definitely possible.

You can give users the opportunity to select an image (and / or video) from their photo library and / or take a new one using the camera, and then use / edit / store it in your application. Check out UIImagePickerController and UIImagePickerControllerDelegate .

You can store images directly in Core Data as a convertible attribute by converting them to NSData using UIImagePNGRepresentation() or UIImageJPEGRepresentation() . If you do, it is recommended that you create a separate object with an image data attribute so that you can quickly load your other attributes (and load image data in all respects as necessary). In addition, you can save images in files in the application document directory and save the file name as an attribute in your entity.

Check out TTThumbsViewController in the Three20 library for a nice way to display a grid of photo thumbnails.

Answer 2

I would recommend storing files in the Documents application directory and storing database paths in them. You can do it differently, but storing them in files reduces the database and gives you more options to load them anywhere without having to load the entire image into memory.