Please do not post the same thing multiple times. The board software automatically flags certain posts as needing moderator attention. This happens the most often for new users. I'm pretty sure this is made clear at the time you attempt to post. Posting the same thing over and over again just makes that many more posts the moderators have to weed through later. This makes us sad. Don't make us sad. If your post/thread doesn't appear, just wait a while. Don't post it again. If it hasn't shown up by the next day, then you can try again. I normally go through posts in the mornings, and try to check a few times throughout the day, but I'm not here 24/7. There will typically be a significant delay before posts are approved. Just be patient.
Hello all new here and new to iPhone/iOS development. I am working on an app that has Tab Bar Navigation to tab between multiple drill down sections (think iPod app on iPhone, only with reference data). It will contain several volumes on information (a tab for each volume). Would it be advantageous to use a plist for each volume or use core data?
Hello all new here and new to iPhone/iOS development. I am working on an app that has Tab Bar Navigation to tab between multiple drill down sections (think iPod app on iPhone, only with reference data). It will contain several volumes on information (a tab for each volume). Would it be advantageous to use a plist for each volume or use core data?
Thanks for any help, Tim
The devil is in the details.
If the amount of data is fairly small (hundreds of records) and you aren't doing a lot of sorting or filtering, arrays and/or dictionaries can be a fine way to represent the data in your app, and then just load/save it from/to a plist.
If you have lots of data, or it's complex (lists of companies, with client and customer relationships between them, and the companies have employees, who have supervisors, subordinates and peers) or you slice-and-dice it in lots of different ways like filtering out only the records that meet certain criteria, or you have tables that can be sorted on multiple keys, etc. then you should probably bite the bullet and use Core Data.
Core Data has a steep learning curve. It will hurt your head at first understanding how it works, and how to use it. However, at some point the light will switch on, and you will be amazed at how powerful it is, and how quickly you can add really cool features to your apps.
Regards,
Duncan C WareTo
Animated GIF created with Face Dancer, available for free in the app store.
Thank you. That's what I figured. I see it has a steep learning curve and I've been working on some of the tutorials to learn. Is it possible to import data from a plist to core data?
twbriggs
Posts: 2New Users
Replies
If the amount of data is fairly small (hundreds of records) and you aren't doing a lot of sorting or filtering, arrays and/or dictionaries can be a fine way to represent the data in your app, and then just load/save it from/to a plist.
If you have lots of data, or it's complex (lists of companies, with client and customer relationships between them, and the companies have employees, who have supervisors, subordinates and peers) or you slice-and-dice it in lots of different ways like filtering out only the records that meet certain criteria, or you have tables that can be sorted on multiple keys, etc. then you should probably bite the bullet and use Core Data.
Core Data has a steep learning curve. It will hurt your head at first understanding how it works, and how to use it. However, at some point the light will switch on, and you will be amazed at how powerful it is, and how quickly you can add really cool features to your apps.
Duncan C
WareTo
Animated GIF created with Face Dancer, available for free in the app store.
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like AwesomeThanks!
- Spam
- Abuse
- Troll
0 • Off Topic Insightful Disagree Dislike Like Awesome