Re: PyObjC
Re: PyObjC
- Subject: Re: PyObjC
- From: Bill Bumgarner <email@hidden>
- Date: Mon, 4 Sep 2006 08:49:51 -0700
On Sep 4, 2006, at 5:10 AM, Daniel GQ Chong wrote:
Just wondering if anyone has any experiences developing with
PyObjC. It
seems like a nice way for beginner like myself to start developing
in Cocoa.
The primary challenge to learning Cocoa is to figure out how to
effectively and correctly use the framework APIs and patterns (KVC,
KVO, delegation, bindings, etc...).
While PyObjC provides a nearly complete bridge such that programming
Cocoa from Python is pretty much just like Objective-C based Cocoa
programming, it is still a bridge environment -- a non-native
environment.
As such, I would still strongly recommend that you first figure out
Cocoa from Objective-C. Learning Objective-C is a very small part of
learning how to effectively program Cocoa.
I've tried to look up for examples of shareware being written
completely in
PyObjC but all I can find are small examples posted in the PyObjC
webpage. I
was wanting to know if this is a suitable path to develop full
featured
software or should I invest more in learning Objective C? Also,
I'll like to
know if the software written in python has the same initial lag
like those
written in java?
There are a growing pool of commercial applications built using
Python/PyObjC. As well, there are a bunch of labs and companies that
use PyObjC extensively for internal development (I used it to vet the
original Core Data APIs at Apple, as an example). So, yes, it is a
production quality tool.
There are a boatload of examples in the PyObjC subversion repository:
http://svn.red-bean.com/pyobjc/trunk/pyobjc/Examples/
ReSTedit is an open source PyObjC Cocoa app that I maintain:
http://svn.red-bean.com/restedit/trunk/
And there are a bunch of PyObjC hacques in my random repository:
http://svn.red-bean.com/bbum/trunk/hacques/
I suppose my real question is that if the same program is written
in python
and Objective C, would the end user experience be any different?
Nope. There is a slightly longer launch time, but nothing compared
to bringing up a JVM. Other than that, a Python/PyObjC based Cocoa
app looks/feel exactly the same as any other Cocoa app (in terms of
the Cocoa generic bits).
You will want to embed the Python interpreter and PyObjC runtime in
your app wrapper. This does increase distribution size. Since most
modern apps have multi-megabytes of random media included in the
distribution, the addition of these bits isn't always significant.
b.bum
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
- Follow-Ups:
- Re: PyObjC
- From: "John C. Randolph" <email@hidden>
| References: | |
| | >PyObjC (From: "Daniel GQ Chong" <email@hidden>) |