Re: Native OS X Development roadmap

On Thu, 13 May 2004, Geoff Ghose wrote:
[...]
> Although approach #1 would simpler in terms of porting, my read is that
> GTK effort is still in its early stages and it could be quite a while
> before it's functional. Also, you wouldn't get to use the great UI
> development environment (like Interface Builder) that OS X provides.
> And finally I fear the end product won't look completely native: for
> example, QT on the Mac definitely has some glitches.

You've answered your own question.  You pays your money and takes your
choice.


> So I'm leaning towards approach #2, and replacing the "Gnome" folder in
> PyblioUI with "Cocoa". (Easy said!) I'm willing to try to take a hack
> at it, but I might not be best person: although I'm familiar with
> Objective-C, my knowledge of python is close to nil. On the other hand
> looking at the PyObjC documentation it doesn't look completely
> insurmountable.
>
> Advice, comments?

I still have it in mind to write a version for a more-portable toolkit
(maybe Qt, maybe wx), now mostly as a first step to a web app version
(probably quixote-based).  (My feeling is that, in order to create a web
app UI, it's wise to tackle a second 'conventional' UI first, to get the
code into a well-factored form.)  Definitely vapourware (I haven't even
looked at 1.3, since I still don't have GTK 2), but if you want to discuss
things, go ahead.


John


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click