Re: [Pyobjc-dev] Best way...??

[<bb...@ma...>]

On Monday, May 19, 2003, at 09:09 US/Eastern, Gary Robinson wrote:
> This app is going to be a cross-platform Python app; we're using Cocoa 
> for
> the Mac interface, but will obviously use other tools for the UI for 
> other
> platforms. (I'm hoping GnuStep will work but we'll see...)
>
> So it looks like the non-PB approach is best, based on your note below.

Sorry -- I'm diving into this conversation late....

For cross platform work, I would suggest you package all the portable 
code using the standard distutils packaging tools (or something 
similar).

For the Cocoa app, PB or buildapp will both work.   PB has an advantage 
in that once the project is indexed, you have excellent integration 
with documentation for Cocoa directly into your project.  In 
particular, I find being able to cmd or opt double click a method to go 
to the declaration or documentation, respectively, to be a tremendous 
boost to productivity.

Also -- for the OS X solution, it is likely that you will eventually 
need to compile some code in for one reason or another.   Maybe 
performance, maybe ease of development, maybe need of accessing APIs 
that are not yet or not easily wrapped....

In that case, you will likely need to have a PBX project -- even if it 
is just a bundle project that is loaded by your pure Python code....

b.bum