Re: WORKAROUND & the Python GUI-lib situation ...

2006-03-15 Thread Chris Mellon
On 3/15/06, robert <[EMAIL PROTECTED]> wrote: > Chris Mellon wrote: > > > > > win32gui and wxPython use *exactly* the same controls in almost all > > (win32ui or win32gui? the later is almost only a better ctypes replacement ) Both. wx wraps native controls. If you see something out of place it's

Re: WORKAROUND & the Python GUI-lib situation ...

2006-03-15 Thread Diez B. Roggisch
> Yes, wx is of course fat. > But I guess things like a layout algorithm ? is done very quickly in a > clean Python only lib. I can just imagine ... No. Layout-engines actually are non-trivial. They use constraint-solvers to do optimization of sizes and offsets. Creating a well-balanced, easy to u

Re: WORKAROUND & the Python GUI-lib situation ...

2006-03-15 Thread robert
Chris Mellon wrote: > > win32gui and wxPython use *exactly* the same controls in almost all (win32ui or win32gui? the later is almost only a better ctypes replacement ) > cases. If you're seeing something "donald duck" then you're either > doing something wrong, or you're using a custom control

Re: WORKAROUND & the Python GUI-lib situation ...

2006-03-15 Thread Diez B. Roggisch
>> > a far better position for most non-trivial UIs, becuase it has >> > infrastructure that win32 (pretty much alone among modern UI toolkits) >> > lacks, like layout algorithms and i18ln support. >> >> Qt has all of this. On all platforms. Just for the record. >> > > I know - so do almost all ot

Re: WORKAROUND & the Python GUI-lib situation ...

2006-03-15 Thread Chris Mellon
On 3/15/06, Diez B. Roggisch <[EMAIL PROTECTED]> wrote: > > wx is also in > > a far better position for most non-trivial UIs, becuase it has > > infrastructure that win32 (pretty much alone among modern UI toolkits) > > lacks, like layout algorithms and i18ln support. > > Qt has all of this. On all

Re: WORKAROUND & the Python GUI-lib situation ...

2006-03-15 Thread Diez B. Roggisch
> wx is also in > a far better position for most non-trivial UIs, becuase it has > infrastructure that win32 (pretty much alone among modern UI toolkits) > lacks, like layout algorithms and i18ln support. Qt has all of this. On all platforms. Just for the record. And layout algorithms - that was

Re: WORKAROUND & the Python GUI-lib situation ...

2006-03-15 Thread Chris Mellon
On 3/15/06, robert <[EMAIL PROTECTED]> wrote: > PyDenis wrote: > > > I fixed problem using Atypes: > > > > import ctypes > > > > ctypes.windll.user32.MessageBoxA(0, 'test', 'Title', > > win32con.MB_ICONINFORMATION | win32con.MB_OK | > > win32con.MB_TOPMOST) > > > > > > It compiles and runs fine wit

Re: WORKAROUND & the Python GUI-lib situation ...

2006-03-15 Thread robert
PyDenis wrote: > I fixed problem using Atypes: > > import ctypes > > ctypes.windll.user32.MessageBoxA(0, 'test', 'Title', > win32con.MB_ICONINFORMATION | win32con.MB_OK | > win32con.MB_TOPMOST) > > > It compiles and runs fine with py2exe. > > > Dont remember buggy pywin32 :) > better use