On 3 Apr 2008, at 13:17, Ronald Oussoren wrote: > > On 1 Apr, 2008, at 22:09, has wrote: >> On 1 Apr 2008, at 19:03, Kevin Walzer wrote: >> >> >>> Yuk. Looks like I will have to remove the Carbon bits from my app at >>> some point! >> >> Or just do what I did with appscript: fork off the bits you need and >> update them yourself. > > I'd prefer if we'd move the interesting bits of the Carbon bindings > to > their own package(s).
As a long-term strategy for Python as a whole, sure. The above suggestion was for Kevin as a solution to his own more immediate needs. > One of the nice things of the current Carbon bindings > is that a large portion of the API is just there and you probably > don't have > to write C code when you want to use an API. > > Sadly enough that's only true of API's that were present in OS9, but > the > idea stands: it would be nice to have complete bindings to the bits of > Carbon that still make sense. Yes, although I'd repeat my earlier suggestion that the most economically viable way to provide Carbon bindings would be to create ObjC wrappers for the Carbon APIs of interest. That way, any language with ObjC bindings, not to mention ObjC itself, can take advantage of these bindings for no extra effort. The more folk you can get using an API, the more likely it is to be well maintained, documented and community supported. One of the reasons the Python Carbon bindings have fallen into disrepair is that there just isn't enough Python folk wanting to use them to justify their development and maintenance costs. Same with Apple's own Java- Cocoa bridge. Targeting ObjC and BridgeSupport to reach the widest possible audience should greatly reduce the risk of failure. Done well, it might even get picked up by Apple in a future OS release. > IMHO that would exclude all GUI-related > code, but I'm a bit biased ;-) I don't think you're being biased. It's just plain good sense to avoid the Carbon GUI APIs where possible now given Apple's own position on them. Other existing Python frameworks (PyObjC, wxPython, etc) already have this area well covered anyway. Cheers, has -- Control AppleScriptable applications from Python, Ruby and ObjC: http://appscript.sourceforge.net _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
