Christopher Barker wrote:
I don't think TK does use native widgets -- it certainly didn't used to.
It was originally built for X11, and got ported to other platforms by
emulating the X11 drawing calls, still drawing its own widgets. I know
they've added support for native standard dialogs, l
Christopher Barker wrote:
> > could build your own app using PyObjC to access the Cocoa GUI, using
> > Python without a Python app bundle.
>
> Can you? Isn't a PyObjC app using the Python executable as the "main"
> app, just like any other python program?
Yes, using the Python executable. But i
Brian Granger wrote:
Some people I am working with feel that doing a framework build is a
bit of a hassle. It means they/we have to support custom build logic
on OS X compared to linux/unix, which I agree is a pain.
no matter how you slice, it you will have to do some custom support for
OS-X
Ronald Oussoren wrote:
> On 14 May, 2009, at 4:31, Bill Janssen wrote:
>
> > I think this depends on what you think the "native Mac GUI" is, and
> > what
> > you want to do with it. For instance, a non-framework build, combined
> > with Xlib (http://python-xlib.sourceforge.net/) works quite wel
Ronald Oussoren wrote:
And to be honest, I even have doubts about a toolkit such as Tk which
uses native widgets but has a rather un-mac feeling unless the developer
really knows what he's doing. That explains why IDLE looks ugly on OSX,
I don't know what I'm doing w.r.t. Tk on OSX, and AFAIK
On 14 May, 2009, at 4:31, Bill Janssen wrote:
I think this depends on what you think the "native Mac GUI" is, and
what
you want to do with it. For instance, a non-framework build, combined
with Xlib (http://python-xlib.sourceforge.net/) works quite well with
the Apple X11 server, which in tu
On 14 May, 2009, at 1:03, Bill Janssen wrote:
Christopher Barker wrote:
Brian Granger wrote:
I seem to recall that a Framework build of Python is needed if you
want to do anything with the native Mac GUI. Is my understanding
correct?
Pretty much -- to access the Mac GUI, an app need