for instance when running on Mac OS X Server or when logged in via ssh,
or when the current interpreter is not running from a fullblown application
bundle. A script runs from an application bundle either when it has been
-started with \program{pythonw} in stead of \program{python} or when running
+started with \program{pythonw} instead of \program{python} or when running
as an applet.
On Mac OS 9 the method always returns \code{True}.
of the folder to show initially,
\var{location} is the \code{(x, y)} position on the screen where the
dialog is shown,
-\var{actionButtonLabel} is a string to show in stead of ``Open'' in the
+\var{actionButtonLabel} is a string to show instead of ``Open'' in the
OK button,
-\var{cancelButtonLabel} is a string to show in stead of ``Cancel'' in the
+\var{cancelButtonLabel} is a string to show instead of ``Cancel'' in the
cancel button,
\var{wanted} is the type of value wanted as a return: \class{str},
\class{unicode}, \class{FSSpec}, \class{FSRef} and subtypes thereof are
and elements declared in the AppleScript class "application". In the
current release that is as far as the object orientation goes, so
in the example above we need to use
-\code{f.get(f.window(1).name)} in stead of the more Pythonic
+\code{f.get(f.window(1).name)} instead of the more Pythonic
\code{f.window(1).name.get()}.
There is one Mac OS X quirk that you need to be aware of: programs
that talk to the Aqua window manager (in other words, anything that has a GUI)
-need to be run in a special way. Use \program{pythonw} in stead of \program{python}
+need to be run in a special way. Use \program{pythonw} instead of \program{python}
to start such scripts.
\subsection{configuration}