No, it really doesn't. They can just create a special file in the
preferences folder and your app can read from that.
again, this is a big deal for small arguments.
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.
sure, i can do that. no problems. thanks to apple, its fun to write
code which will only be useful on OSX. argv parsing is useful
everywhere.
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.
yes, i'm trying to avoid having special-case code for a target
platform for which, in fact, my app doesn't normally need a lot of
special-case code in order for the port to run.
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.
okay, well don't be so lazy. i've got an app i'm porting to OSX, not
writing for OSX. this app has config files, already, a vast plethora
of them in fact, which will be useful for this app when it runs on
OSX. must i convert all of those .xml files to Apples prefs format,
just to get around the hijack of argv?
come on people, OSX is not just a development target, its a port target too ..
The way Mac
users expect an application to work. Not some obscure way that none
of them will have any idea about.
ermm.. which Mac users are you talking about, the ones buying Mac
apps, or the ones who have moved to OSX from Unix and still want to
run the Unix apps they expect to be able to run, smoothly, just like
the good ol' (irix) days?
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.
well, fortunately, editing a .plist is somewhat akin to editing a
Windows shortcut, and pretty much everyone i know, who will run the
apps i'm porting from Unix->OSX, will have no problems with that. if
there is time to over-Apple'ify the port codebase, maybe i will add a
prefpane, a startup items link, an argv list parser Dashboard widget,
an RSS screensaver feed reading my xml files, etc.
but, for now, i just want an easy way to have an argv worth parsing,
and still have a single-click icon that will launch the app. an
Info.plist key for ArgV is a good solution ..
--
;
Jay Vaughan
_______________________________________________
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
