On Sun, Sep 27, 2009 at 10:24 PM, Scott Anguish sc...@cocoadoc.com wrote:
On Sep 28, 2009, at 1:16 AM, Kyle Sluder wrote:
On Sun, Sep 27, 2009 at 10:02 PM, Scott Anguish sc...@cocoadoc.com
wrote:
Why do it? It's easy enough to add your own.
It's also easy to add them to Info.plist… it
On Sep 28, 2009, at 1:34 AM, Kyle Sluder wrote:
Done. rdar://problem://7257097
Also notes that the same collision issue exists for user defaults,
where AppKit stores window and splitter autosave information.
It is unlikely that any apple framework is ever going to introduce a
key of the
Is there a way for me to put my own, custom key into a Cocoa
application's Info.plist and have the application query that key's
setting?
I know that I can use the dictionaryWithContentsOfFile: method of an
NSDictionary to read an arbitrary, dictionary-like property list,
given its pathname.
On Sun, Sep 27, 2009 at 8:33 PM, Hippo Man apple.hippo...@gmail.com wrote:
Is there a way for me to put my own, custom key into a Cocoa
application's Info.plist and have the application query that key's
setting?
Yes, using -[NSBundle infoDictionary]. And of course you can get the
app's bundle
http://developer.apple.com/mac/library/DOCUMENTATION/Cocoa/Reference/Foundation/Classes/NSBundle_Class/Reference/Reference.html#//apple_ref/occ/instm/NSBundle/infoDictionary
Generally one does not put custom keys in the Info.plist. You might
want to consider a separate plist resource for
On Sun, Sep 27, 2009 at 8:47 PM, Kiel Gillard kiel.gill...@gmail.com wrote:
Generally one does not put custom keys in the Info.plist. You might want to
consider a separate plist resource for your target and use NSBundle's
pathForResource:ofType: method to query the dictionary at the resulting
On 28/09/2009, at 1:47 PM, Kiel Gillard wrote:
Generally one does not put custom keys in the Info.plist.
Why not? As long as you're careful to ensure no conflict now or in the
future with Apple's defined keys, you'll be fine (so ensure you use a
key that couldn't possibly be used by
On 28/09/2009, at 2:23 PM, Graham Cox wrote:
On 28/09/2009, at 1:47 PM, Kiel Gillard wrote:
Generally one does not put custom keys in the Info.plist.
Why not? As long as you're careful to ensure no conflict now or in
the future with Apple's defined keys, you'll be fine (so ensure you
Better question...
Why do it? It's easy enough to add your own.
I don't see what the issue is with just adding another. not like
they're hard to read and get access to the data.
On Sep 28, 2009, at 12:23 AM, Graham Cox wrote:
On 28/09/2009, at 1:47 PM, Kiel Gillard wrote:
Generally one
Duh. Not sure what I was thinking. Sorry, Hippo Man. Thanks for the
heads up, Graham and Kyle.
Kiel
Well, many thanks and much appreciation to all of you.
This is exactly the information I was looking for, and it's good to know
that there's a consensus that I _can_ put app-specific info
On Sun, Sep 27, 2009 at 10:02 PM, Scott Anguish sc...@cocoadoc.com wrote:
Why do it? It's easy enough to add your own.
It's also easy to add them to Info.plist… it seems like an appropriate
place to do so.
Perhaps Apple should clarify whether adding custom keys to Info.plist
is condoned.
On Sep 28, 2009, at 1:16 AM, Kyle Sluder wrote:
On Sun, Sep 27, 2009 at 10:02 PM, Scott Anguish sc...@cocoadoc.com
wrote:
Why do it? It's easy enough to add your own.
It's also easy to add them to Info.plist… it seems like an appropriate
place to do so.
Perhaps Apple should clarify
Done. rdar://problem://7257097
Also notes that the same collision issue exists for user defaults,
where AppKit stores window and splitter autosave information.
--Kyle Sluder
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post
13 matches
Mail list logo
