Re: [Pyobjc-dev] Passing a method from PyObjc to Python

[Jordan K. <jkr...@gm...>]

On Mon, 20 Dec 2004 06:08:10 -0500, Bob Ippolito <bo...@re...> wrote:

> Since so much of your code is going to be written in Objective-C and
> not Python, why not just write a plugin that contains your model
> objects?

You'd mentioned previously that the plugin handling was kinda hackish,
so I didn't think it was deployable yet.  Are we talking about the
same plugin procedure?  embed_tutorial or the __plugin_hack__ (sic?)
thing?

> Interface Builder and Xcode probably don't integrate as much as you
> think they do.

I understand that it's all superficial, but I'm trying to give the
client something they can hire someone else to modify (at least the
UI), using standard tools.

> > It would also allow for an easier time with regards to bindings and a
> > few other things in a certain future OS that may not be wrapped yet..
> 
> That doesn't really have anything at all to do with Xcode.

No, but KVO/KVC aren't exactly seamless yet when being passed across
the bridge  -- it has to do with ObjC v. Python, and if I'm writing in
ObjC, why not use Xcode?  To be honest, I don't really care what the
editor is.   All I want is a way to compile the ObjC and the PyObjC
stuff together into an app that works, and all I hear is that plugins
are a hack, that it can only handle one class, or that Xcode is
deprecated.. please correct me if I'm wrong :)

> You can work on that script if you want, but be warned that Xcode
> projects are like pickle files and you're coding against private
> implementation details.  They probably won't change them much, but
> Apple certainly could do whatever they want in a future version of
> Xcode and break everything.

Agreed.. that's not my preferred way of doing things, either.

I'm not complaining, I'm just trying to sort out the best way to
attempt things for this next project.

Thanks again for your help,

J.