Comments on: Rereading Info.plist

By: bdunagan

bdunagan — Fri, 02 Oct 2009 07:00:32 +0000

Yep, totally agree now. I updated this post and wrote a longer explanation in a separate one. Thanks for the swift comments! I already re-implemented the feature!

By: fill the void – Design Iteration

fill the void – Design Iteration — Fri, 02 Oct 2009 06:55:27 +0000

[...] feature I alluded to in my “Rereading Info.plist” post is a logging preference. It has two requirements: user-configurable (i.e. not code) but not [...]

By: Michelle

Michelle — Thu, 01 Oct 2009 17:02:54 +0000

I agree with Stuart. It’s trivial to create a second plist and set up a Config or State class to get/set values. Add one to your template project and all you have to do is change the keys and default values and implement some getters and setters. (I strongly prefer to have a single object interface for data files, rather than having accessors to the data strewn all over my GUI and behavioral code.)

By: Stuart

Stuart — Thu, 01 Oct 2009 12:05:53 +0000

I’ve no idea if there is a formal stance on this from Apple, but I suspect you are misusing the info.plist file. Sure, you can put your own tagged values in, but I don’t feel that info.plist is to be used as a dynamic store. Since it is so easy to, why not just create another file containing a dictionary, and use that? Or store the keyed info in your app’s prefs file, and use notification methods to advice dependent parts of your app whenever keyed values are changed.