I've not read the thread, but I don't understand why you don't like
the normal arg wrapper solution.
because adding another file to the mix that has to be in the package
before things can get fired up is, potentially, a deployment hassle.
just to get argv.
argv is cross-platform.
it irks me enough to want to discuss it with other intelligent people
(whose point of view are far more valuable than my own), because i
depend on it elsewhere, and Apple have removed it, or at least done
all they can to supplant it with their own,
non-other-platform-friendly, replacement ideology. fair enough, but
i hope you understand my point of view doesn't have to be a popular
one to be 'smart', or even smart to be popular.
what i use argv for is as its intended: deployment/command line
configuration, at the command/execution level, for the application at
the surface of its integration with the system. user prefs and data
sync are handled by the app elsewhere, as it should be .. but outside
of that, the cmd line still has a function. even Apple demonstrate
this with the -psn_ switch.
I moved to OSX from Unix, and as a
matter of fact, so have all my friends who run OSX. I don't know
anyone who used a Mac before OSX.
well, i don't use this 'how many people do i know' metric much any
more, the world is full of big and wonderful surprises, and as far as
assessing what technology to actively use.. for me whats important
are the rules of deployment in the sphere of my application.
Me and all my friends keep a Terminal.app open _all_ the time. And
great. do your friends have, say, 3,000 systems to administer in 15
different parts of the world, some of them sustaining mission
critical apps?
we're used to using GUI Apps with argv/arc _all_ the time. Look at
Tcl/Tk. They have Wish.app that you can double-click on and it
brings up a console where you can type commands. They also have
/usr/bin/wish which is a shell script that calls
/Applications/Wish.app/Contents/MacOS/Wish. Look at TextMate, it's a
Cocoa editor that also provides a binary in /usr/bin/tm that lets
you call it from the command line.
sure, i know all about that, i'm a huge fan of the fink and
darwinports lifestyle, got no sweat with any of that. but
terminal.app is not the same thing as a 'single click to get this app
running again' style setup. sophisticated or not, some users must
have this feature with minimal fuss, while still being able to have
their app be administered through broader policies. i want to stay
'as OSX' as i can for the OSX target, while still maintaining the
sanctity of the apps arguments, travelling with it.
On the one hand, you're saying your users need to be able to do
everything from the Finder, on the other hand, you're saying they
would be confortable editing Info.plists files... and you don't want
no, sorry, i'm not being clear on this: the Info.plist is for
deployment/admin, the fact that the args are stuffed in there is so
that Users don't have to sweat the details, and can just carry the
.app bundle with them, as needed. users/admins -can- of course edit
the args, using what they have at hand, and not needing much extra.
plist editor will be onboard, anyway, app bundles already have a
.plist for meta-data, so i'll just use a key in there and pretend its
an 'argv'.
to code anything OSX specific? Seriously, I don't see a solution for
this... something's got to give.
well, as i've already mentioned, i've long since moved on,
technically, on this issue. the continuation of this discourse is,
in my opinion, only worthwhile as long as it reveals insight into the
topic .. and well, maybe there are other carbon issues worth greater
energy .. my scope for OSX on this issue is, as i said, from that of
a port target..
--
;
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
