Well! As per usual, after hours of frustration as soon as I send off an
email I discover the answer for myself.
For those who are curious there is an objc method objc.parseBridgeSupport
which converts xml data to the necessary python objects.
so the code looks like this:
f =
open('/Library/Frameworks/frameworkgoeshere.framework/Versions/A/Resources/BridgeSupport/PyObjC.bridgesupport')
objc.parseBridgeSupport(f.read(),
globals(),"/Library/Frameworks/frameworkgoeshere.framework")
On Tue, Jan 19, 2010 at 12:41 PM, Ben Jack <benthej...@gmail.com> wrote:
> Hi there,
> I am currently delving into pyObjC, but have been running into some
> difficulty's with using the bridgesupport files for the framework I am
> using.
> I have the basics working using objc selectors for example if I have a
> delegate function buttonChanged_isPressed_ (int1, int2) :
> buttonChanged_isPressed_ = objc.selector(buttonChanged_isPressed_,
> signature='v...@0:4i8B12')
>
> but It seems to me like this is just restating what the bridgesupport file
> has already defined (I don't think it is even being properly loaded when I
> load the framework). I could possibly keep defining these signatures for
> functions, but my problem is with the low level c structures which aren't
> understood by python.
>
> I have this project working fine in ruby, which reads the bridgesupport
> file when I load the framework and does all the dirty work as far as
> creating signatures for me.
>
> Essentially what I am asking is, is there any simple way to direct python
> to the bridgesupport file when I load up the framework, and does this negate
> the need to specifically create selectors for my delegate functions?
>
>
> cheers,
> Ben
>
_______________________________________________
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
