How is "binary" plist different from "classic" plist (which I
prefer and seemed about as small as you could make it, yet remained
vi friendly)?
...one is in binary and the other is in UTF-8 XML. They are vi
friendly with a simple use of a conversion tool, heck on a Mac OS X
you could use a little piping magic and be done with it.
In Tiger, CFPreferences now writes out its property lists in the
binary plist format. Panther will read these plists without
modification, although it will write plists as XML. The binary format
is smaller in all cases - for preferences plists that have structures
like arrays of dictionaries where each dictionary has the same keys,
the new plist on disk may be 2 or 3 times smaller.
You can share a home directory between Tiger and Panther without
issue. Should you need to rewrite a plist manually for some reason
you can either convert the plist using plutil(1) or just open it up
and edit it using the Property List Editor application.
-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
