views:

45

answers:

2

By best I mean most efficient. So don't go on about subjectiveness.

I have a list of websites and I want to store the list on the iphone locally, there must be an URL, title and a small image (like 32x32 max image size). I don't think I should be using CoreData for this. Should I be using a plist?

EDIT: Efficient's definiton i though was obvious. Take up the least amount of room, use lowest memory/CPU.  Sorry i forglt to say About 10-15 max items. And they just get loaded into a table view when the app first loads or when that view is brought back by a nav controller.  

A: 

You say not to "go on about subjectiveness" but you don't provide your definition of efficient for this.

You don't specify how many websites you want to store or how you want to use them or what is important to you - storage size, i/o perf, ability to query in specific ways etc.

It doesn't sound like a plist would be a bad fit but I guess my earlier point is just that way you are going to read, write data is generally equally or more important in setting context for questions like this.

Nick
A: 

If you can, leave the images in the resources, and put the url, title and imagename in a pList. Alternatively, you could just create a "Site" class with the three properties, and generate an array of Sites in code. (Or an Array of Dictionaries)

Andiih
well the list has to be "staying", sorry i've forgotten the proper terminology. But it keeps the list between running the app.
Jonathan
If you are seeding the list initially, use a pList. Otherwise just store your array in NSUserDefaults
Andiih