Diez B. Roggisch wrote:
[color=blue]
> Philippe C. Martin wrote:[color=green]
>> Hi,
>>
>> Is wxWidget now part of python ? or will it be ?[/color]
>
> 1) No. 2) I guess no. Because it has pretty heavy dependencies (wx,
> GTK/other toolkit)
>
>
> Tkinter is what comes ou of the box - and thats it.
>
> Regards,
>
> Diez[/color]
Hello Philippe,
[color=blue]
> Is wxWidget now part of python ? or will it be ?[/color]
No, I don't think it will ever be part of Python. But, wxWidgets is written
in C++, so it has nothing *pythonic* in it. There is, however, a "Python
Binding" of wxWidgets, called (obviously ;-) ) wxPython. If you can install
a site-package, I would suggest you to visit http://www.wxpython.org/.
wxPython has a very active newsgroup and a lot of nice user contribution. If
you can not install a site-package, I think that Tkinter is the only choice
you have (but I may be wrong here).
HTH.
Andrea.
--
"Imaginatio n Is The Only Weapon In The War Against Reality."
Gian Mario Tagliaretti enlightened us with:[color=blue]
> No, and *I hope* that if another toolkit has to replace Tkinter
> (will never happen?) will be PyGTK... :)[/color]
Why do you hope for PyGTK? I think one of the strengths of wxWidgets
is that it uses the native platform's look. GTK looks very nice on my
Gnome desktop, but to be honest it's rather ugly on Windows or Mac.
Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?
Frank Zappa
PyGTK is just easier to code with. The api is much nicer. However,
yeah, the windows/mac appearance probably does make it a non-starter,
unfortunately. As near as I can tell, the solution that currently has
the most momentum is to just integrate the cheeseshop more tightly into
python, so that whatever gui toolkit you choose can be installed
easily. Its probably the only politically feasible solution anyway.
On 6 Nov 2005 12:08:23 -0800, gsteff <greg.steffense n@gmail.com> wrote:
[color=blue]
> PyGTK is just easier to code with. The api is much nicer.[/color]
That's why I think that Dabo's UI module is the best of all worlds. It
wraps wxPython, so the controls look great on any platform, but
provides a cleaner and more consistent API than raw wxPython. I almost
never have to look up how to do something in Dabo, whereas I couldn't
program in wxPython without the docs open.
Philippe C. Martin wrote:[color=blue]
> Thanks, Tkinter it is.[/color]
It really depends on what you want to achieve. If you want to
make any advanced GUI application, you'll probably want some
third party extension to Tkinter anyway, and then you might
as well choose another tool kit from the beginning, whether
it's wxPython, PyGtk or PyQt. It's not more inconvenient to
rely on wxPython than to rely on e.g. Pmw (2 years since last
release).
batfree enlightened us with:[color=blue]
> Now GTK can use the local theme.You can choose the local theme to
> make your application windows style on Winodws and Mac likely on mac
> os.[/color]
But why do that yourself, when you can use a GUI toolkit that does it
for you?
Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?
Frank Zappa
batfree enlightened us with:[color=blue]
> Now GTK can use the local theme.You can choose the local theme to
> make your application windows style on Winodws and Mac likely on mac
> os.[/color]
But why do that yourself, when you can use a GUI toolkit that does it
for you?
Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?
Frank Zappa
Comment