Brian Stevens a écrit :
> 
> On Feb 8, 2006, at 9:33 AM, Bernie wrote:
> 
>>> I'm ashamed to say that all the FB apps I've been testing don't use 
>>> CFPreferences.
> Just wanted to share my success using the new CFPreferences written by 
> Bernie & RP and thank them both for the effort to build these functions 
> for us. My app's next rev will reflect this conversion. Take my apps 
> name off your list Bernie.
> 
> BTW: It only took a few hours to implement once I understood which 
> functions to use for the preferences and they are all easy to use. Since 
> my app has 40+ items to save in a preference file, it was a good 
> real-world test.
> 
> Thanks again Bernie and RP.
> 

Count me in. I'm on the way to converting my prefs to CFPreferences, but 
I'm stuck at the moment with a specific problem whose solution eludes me.

We've been used to store file information as aliases in the resource 
fork of our preference files, haven't we? Now that resources are 
deprecated in OS X, what is the correct way to handle such a situation?

In the first plist I have examined, I have seen a file path and I 
thought that was the new method recommended by Apple. I modified my 
program so that it could store that info in the preference file. So far, 
so good. But, all my attempts to convert back the file path to an 
FSSpec, via an FSRef, have failed up to now.

Furthermore, I'm not sure this is really the way to go, because if the 
end-user changes in the Finder any folder name belonging to the path or 
the file name, I believe the path will be broken.

Anybody has an answer to this question?

Alain