OK-- I "fixed" the problem with forwardInvocation: being invoked on
NSProxy. Was a matter of not passing -forwardInvocation: off to super
in OC_PythonObject.m.
It seems to kind of fix the problem. However, after a couple of runs of
HelloWorld.py, I'm no longer able to execute that script due to a Window
Manager issue-- either with the original version or new version of
OC_PythonObject.m.
As such, I really think we need to do two things:
- rewrite the PyObjC bridge entirely and aim it *only* at solving
the Foundation and below problem (while removing cruft from almost 8
years ago, at this point)
- write a new module that leverages pyobjc and adds the necessary
support for dealing with AppKit based scripting. In particular, I'm
thinking of putting together a python module (via distutils) that
contains an application wrapper with all the appropriate glue. Invoking
a script that wants to use the appkit would import this module and call
into it with a reference back to the object that wants to be the app
delegate. The module would then launch in the same fashion as any
normal AppKit project, but would look to the python world for all app
related constructs.
Hmmm... gotta give this thought.
On a related note, I have a couple of frameworks that bind the python
interpreter into a Cocoa/Objc/WebObjects app such that you have a Python
Interpreter ObjC object that you can toss arbitrary bits o' python code
at.... including "import pyobjc".
b.bum
|
