Re: what is the proper place to store application settings
Re: what is the proper place to store application settings
- Subject: Re: what is the proper place to store application settings
- From: Jeff LaMarche <email@hidden>
- Date: Wed, 9 Apr 2008 14:41:02 -0400
I'm assuming that these will change, but should not be changed by the
user, correct?
It seems to me that you'd want to avoid compiling them into your
classes using #define, I think a property list included as bundle
resource is the way to go.
http://developer.apple.com/documentation/Cocoa/Conceptual/PropertyLists/PropertyLists.html
On Apr 9, 2008, at 2:19 PM, Laimonas Simutis wrote:
I started programming with Cocoa recently. Created an application
which makes REST calls and displays the response values in a simple
window. For each particular REST function I have a corresponding class
which defines functionality for constructing a proper URL needed to
call a function, initiating the call and informing the interested
delegate object once the REST response is received.
Right now I have the host part of the url hardcoded in each class that
represents a different REST function call. I know I should store it in
one place, not sure what's the recommended "place" in cocoa apps. I
was thinking maybe one class with #defines and then all the REST
representing classes would include that? Also I see some docs
mentioning plist setting files, could that be a better place? Based on
my environment (debug, testing, prod) this url will change as well.
Thanks for any recommendations,
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden