On Feb 7, 2006, at 10:39 PM, Bernie wrote:

> I'm ashamed to say that all the FB apps I've been testing don't use  
> CFPreferences.
Herbie is right. My plist file was created when testing Bernie's  
CFPreferences demo.  My app is one of the culprits here that doesn't  
use CFPreferences. It is on the to-do list. In defense of those who  
haven't gone the CFPreferences route, the current method (using a  
record structure with GET/PUT Prefs) is quite simple and does the job  
well. Also, at least in my specific case, converting to CFPreferences  
is not a trivial project (it would be with fewer preferences). In my  
app there are approximately 20 preferences in a record (that is now  
global and available when needed with no further coding) and every  
place the preference is consulted needs to be changed to do the  
CFPreference "get".  Also, when a preference changes the CFPreference  
"put" needs to be done (unlike the current method which just changes  
the in-memory global record and does one put at quit time). Clearly,  
this isn't a major project, but the differences are enough to require  
hours of code changes and many more hours testing to make sure  
nothing is busted.

All that being said, there are clear benefits to using CFPreferences  
(which have been detailed on the list --I think). CFPreferences is  
clearly where we need to be, and would be my choice for a new  
project. However, conversions, while basically simple, are still a  
lot of work. Just my 2 cents.

Brian S.