views:

570

answers:

1

Hi All,

First of all, while I have an understanding of some of the basics, I'm am still somewhat of a newbie.

I have a sectioned UITableView that I am currently using NSDictionary(for grouping) and 4 or 5 different NSArrays (for data, some of which gets passed to the next view when a cell is selected) to populate the table. It works but it's a very long list and after a few minutes of scrolling the UITableView up and down, leaving that view and coming back to it, the app starts to "slow down" and eventually freezes. I have been doing some research and have found that the way I am doing that is not the best way. I have read about using another object to populate the table which will only load data as needed and won't keep that data in memory(which is probably causing my app to freeze).

Can anyone help point me in the right direction to build a "data object" to store my data and then use it in my UITableVIew? Can I just take my NSDictionaries and NSArrays and somehow put them in thier own class and call that class? Would I use Core Data? Any other suggestions? As a note, this data cannot be added to, updated, or deleted by the user. The only time I will change the data is to add more data(a completely new record) to make the list longer and maybe once in a while, but very rarely, updated or deleted by me.

Any help would be greatly appreciated.

Thanks!