I started experimenting with PyObjC last night. Specifically, I was trying to get the first example program in the NSController going in Python, after I got it working in Objective-C. I wasn't successful, but at least I understand what the problem was: I didn't write enough support code.

I originally thought that all I had to do was copy the nibs I created for the ObjC version, and then implement the Converter class in Python. Alas, it was not so simple, for I realized that Xcode creates other helpful classes that I needed to code in Python as well. So tonight I'll do that.

My impressions of PyObjC so far is that it's way too easy. There's got to be a monster hiding in the background somewhere, something that's going to make it tougher than it looks. But that's just programmer paranoia working in the background. Too many times, working with something that seems clean and elegant, everything goes fine until the coding situation turns non-trivial, and then the whole house of cards comes down. Like, everything is cool until you go multithreaded. Or there's a problem with connecting to multiple databases. Or something else. I've been burned too many times by marketing promises that my life is incomplete without some product they sell.

But I have high hopes. I always do.

9:00:18 AM    comments ()  trackback []