No, it really doesn't. They can just create a special file in the
preferences folder and your app can read from that.
Furthermore, every single mac GUI Application tailors its user
experience based on preferences set by the user. I have no idea why
you can't do that as well. Just have a preferences window the user
sets.
I think the entire problem is that you're expecting OS X to behave in
a specific way and are unwilling to code anything that's OS X
specific.
You say an option is a config xml file. That's what CFPreferences and
registering default values are for. I've yet to see any reason why
you want OS X to behave the way you're suggesting other than you're
being too lazy to do it the proper OS X way. The way Mac users expect
an application to work. Not some obscure way that none of them will
have any idea about.
And editing an info.plist file is infinitely more difficult for a
user to accomplish than it is for you to simply add a checkmark in
your preference dialog.
Ack, at 9/23/05, Jay Vaughan said:
At 23:49 -0700 22/9/05, Rosyna wrote:
Maybe I'm being slow here, I haven't read the entire thread. But
what's wrong with using defaults (man defaults) to set these? Easy
as pie. Sword pie.
yeah, thats another good suggestion in the 'user must open terminal'
realm, and would work, but i want a clean Finder experience that
'allows for argv', mostly..
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
