On Jun 29, 2009, at 8:55 PM, Dave Keck wrote:
Don't abuse property lists; if you need a database, use a database.
Indeed. And if you can/aren't already, use a binary plist. And load
the data in a background thread, to keep the UI snappy.
Without any additional information, I would suggest i
> Don't abuse property lists; if you need a database, use a database.
Indeed. And if you can/aren't already, use a binary plist. And load
the data in a background thread, to keep the UI snappy.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Ple
> How can I make the application load that 6,3MB property list file
> faster?
Don't abuse property lists; if you need a database, use a database.
--
Scott Ribe
scott_r...@killerbytes.com
http://www.killerbytes.com/
(303) 722-0567 voice
___
Cocoa-dev
On Jun 29, 2009, at 9:35 AM, Philip Juel Borges wrote:
I have an app that where a toolbar button loads a property list
file into 3 tableviews, which in turn updates a webview. The file is
6,3MB. Whenever I press the button it takes roughly 2 seconds.
How can I make the application load t
Hi!
I have an app that where a toolbar button loads a property list file
into 3 tableviews, which in turn updates a webview. The file is 6,3MB.
Whenever I press the button it takes roughly 2 seconds.
How can I make the application load that 6,3MB property list file
faster?
/Philip