Re: Table View Blues (summary)

FROM : Scott Anguish
DATE : Fri Nov 22 08:04:03 2002

Keep in mind that the datasource doesn't hve to be an array.. it
doesn't have to be in memory all at once.  Only the cells on the screen
need to be populated with objects at the time.


On Friday, November 22, 2002, at 01:33 AM, Sam Griffith wrote:

> On 11/21/2002 5:21 PM, "Sheehan Olver" <<email_removed>> wrote:
>
>> No, I understood what you meant. The key is he wanted something that
>> could scale. In order to reuse NSStrings you need to keep them in
>> memory. Say instead of 100,000 records, there were a billion cells in
>> the table (remember, the solution should be something that could
>> scale). This means if you reuse the NSStrings you could have a billion
>> extra NSStrings sitting in memory. Not only that, but when the table
>> is
>> closed you would have a billion NSStrings to dealloc. The fact is,
>> creating and destroying NSStrings is extremely fast compared to human
>> reaction time, meaning if you create 100 NSStrings at once, the user
>> won't notice. But it doesn't hold up to deallocating a billion
>> NSStrings at once.
_______________________________________________
cocoa-dev mailing list | <email_removed>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.