| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
in MacPython-OS9 and MacPython-OSX (or the equivalent unix Python on
Mac OS X). The only items remaining in Mac/Lib are modules that are
meaningful only for MacPython-OS9 (CFM stuff, MacPython preferences
in resources, etc).
|
| |
|
|
|
| |
OSX 10.2 apple-supplied Python as its base: if we've copied a symlink
as the executable we remove it and install appletrunner in stead.
|
| |
|
|
|
| |
to it.
- Allow for symlinks in the applet template.
|
| |
|
|
|
|
|
|
|
|
| |
dialogs are now stored in Mac/Lib, and loaded on demand through macresource.
Not only does this simplify a MacPython based on Apple's Python, but
it also makes Mac error codes come out symbolically when running command
line python (if you have Mac/Lib in your path).
The resource files are copied from Mac/Resources. The old ones will disappear
after the OS9 build procedure has been adjusted.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
This is a silly workaround for a rather serious bug in MacOSX: if you take
a long filename and convert it to an FSSpec the fsspec gets a magic
cooky (containing a #, indeed). If you then massage the extension of this
fsspec and convert back to a pathname you may end up referring to the
same file. This could destroy your sourcefile. The problem only occcurs
in MacPython-OS9, not MacPython-OSX (I think).
Closes bug #505562.
|
| |
|
|
|
| |
check whether it contains a .nib, and do the Cocoa song and dance if
it does.
|
| |
|
|
|
|
|
|
|
| |
argv emulation (i.e. if the end user drops files and folders on the
applets these will show up in sys.argv) BuildApplet will add the required
code to the applet bundle, in __rawmain__.pyc.
This code is compiled from appletrawmain.py, it creates sys.argv, cleans
up most of the mess and executes either __main__.py or __main__.pyc.
|
| |
|
|
|
| |
- The applet .rsrc file should be called python.rsrc, it is not based on the
applet name.
|
| | |
|
| |
|
|
|
|
|
| |
verbose output to the console, etc.
- Allow Cocoa applets to be built with BuildApplet.
No full testing has been done yet to ensure OS9 operation hasn't suffered.
|
| |
|
|
|
| |
Also, for now (until we learn to parse .plist files) we make a special case
for the IDE, setting the creator to "Pide".
|
| |
|
|
| |
enough that IDE and BuildApplet can create applets, yeah!
|
| | |
|
| |
|
|
| |
Carbon applets and vice-versa.
|
| |
|
|
| |
Don't call OpenDeskAcc() and AppendResMenu() on Carbon.
|
| |
|
|
|
|
| |
allows multiple simultaneous copies to be run from a server, and Applets shouldn't
write their datafork so it appears safe.
|
| |
|
|
| |
applet-specific rsrc file we add a "Pyta" owner resource. Owner resources have both id=0 and name="Owner resource" (is this always true?).
|
| |
|
|
| |
resulting program is called PythonInterpreter.
|
| | |
|
| | |
|
| |
|
