Commit Graph

6 Commits

Author SHA1 Message Date
Jack Jansen 122f87fa04 The interpreter popup was never filled with any data, fixed.
Fixes #775878.
2004-07-16 12:36:02 +00:00
Jack Jansen d7cccdd591 Added a field that allows the user to set sys.argv-style arguments
to the script. Fixes #757544.
2003-06-20 22:21:03 +00:00
Jack Jansen 3d3b74677a Optionally honour #! paths in scripts. Fixes #676358. 2003-02-17 15:40:00 +00:00
Jack Jansen f044e090c4 Changed the input field for the interpreter to use (in the preferences
window) to a combobox listing the known interpreters.
2002-12-26 22:10:53 +00:00
Jack Jansen 2095c06cec Lots of restructuring, mostly suggested by Bill Bumgarner. Main
externally visible difference is that the factory defaults are
now in a plist file in the bundle, in stead of being hard-coded in
the application.
2002-11-25 13:11:06 +00:00
Jack Jansen 3bbb617ca4 First stab at the launcher application. This will be run when the user
doubleclicks a .py, .pyw or .pyc file. It runs the file by invoking the
relevant interpreter (either the command line Python in a terminal window
or a Python.app for GUI-based scripts). Interpreter to use and the options
to pass are settable through preferences.

If PythonLauncher wasn't running it does its thing for one script and exits.
If it was manually started before a dialog is presented where the user
can set the options to use, etc.

To be done:
- option-drag/doubleclick should always open the interactive dialog
- Terminal-window isn't done yet
- Should be reimplemented in Python, but pyobjc isn't part of the core.
- Various menu entries should be disabled.
2002-07-29 21:36:35 +00:00