tags:

views:

15

answers:

0
Q: 

Using Core data to store objects(pointing to seperate views) in a NSMutableArray .

Hello All,

I am new to the iOS. Currently, I am using 3.1.3 base SDK for development and testing. I am developing an application to store credentials. In my Main menu, I have a NSMutable Array with some default cells(objects in NSMutableArray speak) and then the option to add some arrays.Currently I am able to add new cells and remove cells - without persistence across app relaunches....

Each object points to a new view. I wish to use Core Data to store these objects(and the views associated) so that I can store user added cells and the default cells as well. Any Ideas if Core data could wield itself to cells linked with views? or am I barking up the wrong tree?

Cheers, George.

related questions

Save CoreData-entities in NSUserDefaults
"Save" in CoreData-apps
How to get some values from CoreData-Entities to code.
Shared Objects in Cocoa
Is there a Java equivalent to Apple's Core Data?
When is an NSPersistentDocument's data store moved to final save location?
Data Store for a Mac/iPhone Hybrid App
How to give title to NSPersistentDocument window
Programmatically Update an attribute in Core Data
Syncing a Core Data Model With A Web Service
Adding an image to NSPersistentDocument
What is the best way to model an Association Class in Core Data?
Manual Core Data schema migration without "document changed" warning?
Code review for many-to-many relationship UI implementation in CoreData
Sending fetch message to NSObjectController inside a modal loop.
Can you Bind to the timeInterval attribute of an NSDatePicker?
What are the factors to decide between using Core Data versus rolling out a custom model?
How do I customize an array controller's fetch request in Core Data?
Fetching Core Data entities, but not sub-entities
Error handling in Core Data
Modifying NSDatePicker for automatically generated predicate row templates
Automatically generated predicate row templates for to-many key?
Cross-model relationships in NSManagedObjectModel from merged models?
setPrimitiveValue:forKey: and to-many relationships
Is it safe to manipulate objects that I created outside my thread if I don't explicitly access them on the thread which created them?