>>> When a script is installed somewhere central, like /usr/local/bin,
>>> that's really all that makes sense.
>>
>> That's clearly irrelevant, because people aren't going to be double-
>> clicking on files that you have to do "magic incantations" to even
>> see from Finder.
Fair enough, but what about /Applications, etc?
> The main problem here is that there isn't really a "current" directory
> in the GUI experience.
That's what I meant by "it all goes to heck"
> That's why normal application bundles start with
> / as the CWD.
Which is a poor choice: these really should default to $HOME. I'm sick
of accidentally dumping MSExcel files in my root directory. I can't
think of any time anyone should ever put anything in (or get anything
from) /. Most applications should only ever be manipulating files inside
$HOME.
>> I have never in my life seen a script that must be started
>> with a working directory of $HOME (unless it also lives there). It is
>> however extremely common for scripts to require that they are run
>> from the directory they live in.
OK I'm sold (not that I needed to be).
There are instances, however. For example, SPE isn't built as an .app. I
have a friend that has set it up to click on it and PythonLauncher
starts it. In that case, $HOME makes more sense. However, the real
solution is to build an .app or applet with it.
> Nope, that's not possible. If you want argv emulation you'll have to
> build an applet.
That does seem the best solution.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
[EMAIL PROTECTED]
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
