On Tue, 10 Jul 2001, Andrew Zeldis wrote:
> > Subject says it all...
> I myself have become convinced that the gap between python and cocoa is big
> enough that, for the purpose I wanted (interactive experimentation with
> cocoa) other solutions are better. Joy (commercial) and F-script (free)
> come to mind.
> For developing applications in python, IMO, a more pythonic framework built
> around the cocoa classes would be useful. The python-Objective-C
> translation works well, but it's not pretty... Also, I don't think anyone
> has solved the bootstrapping problems with getting an NSApplication up and
> running (with python objects as delegates, etc).
The other reason things have been quiet is that we're heading towards
a major rewrite -- we need to make ObjC objects into not just Python
objects, but Python classes that are fully subclassable. There is a
way to do this now with Extension Classes: this is used in Zope and
the Boost C++ libraries, but it relies on a hack that may be changed --
this has been under discussion on the Python-Dev list -- there is
an initial implementation of the new method in the python-dev cvs
tree, but I haven't had a chance yet to download it and look at how
it differs from the old method. ( Since the plan is to reduce or
eliminate the difference between classes and objects and to make
built-in objects subclassable, it's possible that not much new will
have to be done to enable this feature. )
Being able to subclass objective-c classes in Python (which thru
the bridge, will appear as objective-c classes to Cocoa ) will make
it much easier to do Cocoa programming in Python.
-- Steve Majewski