Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #81060 > unrolled thread

GUI toolkit(s) status

Back to article view | Back to comp.lang.python

Contents

  GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-19 23:59 -0800
    Re: GUI toolkit(s) status Paul Rubin <no.email@nospam.invalid> - 2014-11-20 00:25 -0800
      Re: GUI toolkit(s) status Chris Angelico <rosuav@gmail.com> - 2014-11-20 19:40 +1100
        Re: GUI toolkit(s) status Christian Gollwitzer <auriocus@gmx.de> - 2014-11-20 10:04 +0100
          Re: GUI toolkit(s) status Chris Angelico <rosuav@gmail.com> - 2014-11-20 20:17 +1100
          Re: GUI toolkit(s) status Terry Reedy <tjreedy@udel.edu> - 2014-11-20 23:34 -0500
            Re: GUI toolkit(s) status Paul Rubin <no.email@nospam.invalid> - 2014-11-20 20:49 -0800
              Re: GUI toolkit(s) status Christian Gollwitzer <auriocus@gmx.de> - 2014-11-21 08:57 +0100
            Re: GUI toolkit(s) status Kevin Walzer <kw@codebykevin.com> - 2014-11-21 09:13 -0500
              Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-22 00:59 -0800
                Re: GUI toolkit(s) status Kevin Walzer <kw@codebykevin.com> - 2014-11-22 12:40 -0500
                  Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-22 10:49 -0800
            Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-21 12:38 -0800
              Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-21 12:49 -0800
            Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-22 10:33 -0800
              Re: GUI toolkit(s) status Christian Gollwitzer <auriocus@gmx.de> - 2014-11-22 20:34 +0100
                Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-24 11:24 -0800
          Re: GUI toolkit(s) status Kevin Walzer <kw@codebykevin.com> - 2014-11-21 09:05 -0500
          Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-21 12:15 -0800
          Re: GUI toolkit(s) status Michael Torrie <torriem@gmail.com> - 2014-11-21 21:07 -0700
            Re: GUI toolkit(s) status Dave Cook <davecook@nowhere.net> - 2014-11-26 09:40 +0000
              Re: GUI toolkit(s) status Mark Summerfield <list@qtrac.plus.com> - 2014-11-26 03:47 -0800
                Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-26 06:36 -0800
                  Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-26 07:11 -0800
              Re: GUI toolkit(s) status Michael Torrie <torriem@gmail.com> - 2014-11-26 20:19 -0700
          Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-22 00:12 -0800
          Re: GUI toolkit(s) status wxjmfauth@gmail.com - 2014-11-22 02:46 -0800
          Re: GUI toolkit(s) status Ian Kelly <ian.g.kelly@gmail.com> - 2014-11-24 08:18 -0700

Page 2 of 2 — ← Prev page 1 [2]

#81554

On 2014-11-22, Michael Torrie <torriem@gmail.com> wrote:

> I can't speak for wxWidgets, but when I last looked at it years ago it
> fairly reeked of MFC-style GUI programming with event tables instead of
> a nice, flexible signal/callback interface.  Has this changed?

In Python?  I've been using wxpython for 6 or 7 years, and it's always
used callbacks in Python.  The API is not as polished or extensive as
Qt, but it's still very capable.  I think it's easier to write custom
widgets in wxpython because there are so many examples to follow.

Recently I decided to use PyQt for a project that was required to run
on win32 and OS X, and for some reason my layout, wich was fine under
win32, was screwed up on OS X.  I switched back to wxpython 3.0, which
looks very good under OS X.  

Dave Cook

[toc] | [prev] | [next] | [standalone]

#81562

I've done a fair bit of Python GUI programming, so here's my 2c.

Tkinter is small, fast, and v. frustrating to use (but maybe the latter is just me). It looks good on Windows (from 8.5), ugly on Linux, and OK on Mac (but you have to do a fair bit of if MAC do this else do that.

The next three work on Win/Mac/Linux:

wxPython is available for Python 3 (as Phoenix) but it is big and there are lots of "near duplicate" widgets so it is quite hard to find the right ones to use. The docs don't have many examples and aren't fully updated for Phoenix which is still under development.

PySide works only with Qt 4. It is big but easy to install. However, I don't know how long it'll be supported and it hasn't been ported to Qt 5 (yet).

PyQt works with Qt 4 and Qt 5 is solid but is dual licensed. And it is big of course.

PyGObject (PyGtk's successor) is very nice in principle but effectively Unix only. I've never managed to create version-specific instances of it (to test against particular versions), something that's easy with PySide and PyQt (don't know about wxWidgets).

There's kivy which claims to be cross-platform but I haven't tried it.

And there is a pure-Python GUI initiative: PyGUI, but I'm not sure if that's still going or has got stuck.

I really hope that PyGUI or some other pure-python (+ maybe ctypes) GUI library is created for Python, but it is a really major undertaking...

[toc] | [prev] | [next] | [standalone]

#81568

Le mercredi 26 novembre 2014 12:48:04 UTC+1, Mark Summerfield a écrit :
> I've done a fair bit of Python GUI programming, so here's my 2c.
> 
> Tkinter is small, fast, and v. frustrating to use (but maybe the latter is just me). It looks good on Windows (from 8.5), ugly on Linux, and OK on Mac (but you have to do a fair bit of if MAC do this else do that.
> 
> The next three work on Win/Mac/Linux:
> 
> wxPython is available for Python 3 (as Phoenix) but it is big and there are lots of "near duplicate" widgets so it is quite hard to find the right ones to use. The docs don't have many examples and aren't fully updated for Phoenix which is still under development.
> 
> PySide works only with Qt 4. It is big but easy to install. However, I don't know how long it'll be supported and it hasn't been ported to Qt 5 (yet).
> 
> PyQt works with Qt 4 and Qt 5 is solid but is dual licensed. And it is big of course.
> 
> PyGObject (PyGtk's successor) is very nice in principle but effectively Unix only. I've never managed to create version-specific instances of it (to test against particular versions), something that's easy with PySide and PyQt (don't know about wxWidgets).
> 
> There's kivy which claims to be cross-platform but I haven't tried it.
> 
> And there is a pure-Python GUI initiative: PyGUI, but I'm not sure if that's still going or has got stuck.
> 
> I really hope that PyGUI or some other pure-python (+ maybe ctypes) GUI library is created for Python, but it is a really major undertaking...

I worked and experimented with everything you described
since, well I do not remember. (It should be possible to
find some of my comments in wxPython dev archive at the
wxPython 2.(0|1)? time).

That's why I wrote and initiated this thread:

"""
The single (not too buggy) GUI toolkit for CPython [*],
which works smoothly, coherently and *SAFELY* is
one of the Qt derivatives for Python 3.2.
(If used properly, one can cover [corrected] the whole
Unicode range).

Today, there are simply no more valid and working
GUI toolkits [corrected] running "out of the box". 
"""

jmf

[toc] | [prev] | [next] | [standalone]

#81581

[Completely off topic]

I'm too old for this. If I were a beginner targeting
serious GUI destop applications, I would look at
.NET framework.
In my understanding, MS is opening it!

jmf

[toc] | [prev] | [next] | [standalone]

#81614

On 11/26/2014 02:40 AM, Dave Cook wrote:
> On 2014-11-22, Michael Torrie <torriem@gmail.com> wrote:
> 
>> I can't speak for wxWidgets, but when I last looked at it years ago it
>> fairly reeked of MFC-style GUI programming with event tables instead of
>> a nice, flexible signal/callback interface.  Has this changed?
> 
> In Python?  I've been using wxpython for 6 or 7 years, and it's always
> used callbacks in Python.  The API is not as polished or extensive as
> Qt, but it's still very capable.  I think it's easier to write custom
> widgets in wxpython because there are so many examples to follow.
>
> Recently I decided to use PyQt for a project that was required to run
> on win32 and OS X, and for some reason my layout, wich was fine under
> win32, was screwed up on OS X.  I switched back to wxpython 3.0, which
> looks very good under OS X.  

What kind of layout did you use?  I've never had this problem with Qt or
Gtk.  Even when the font sizes and screen resolution changes. That's the
beauty of the self-adjusting layouts.

[toc] | [prev] | [next] | [standalone]

#81279

Le jeudi 20 novembre 2014 10:04:40 UTC+1, Christian Gollwitzer a écrit :
> Am 20.11.14 09:40, schrieb Chris Angelico:
> > On Thu, Nov 20, 2014 at 7:25 PM, Paul Rubin <no.email@nospam.invalid> wrote:
> >> wxjmfauth@gmail.com writes:
> >>> Today, there are simply no more valid and working
> >>> GUI toolkit running "out of the box".
> >>
> >> Tkinter still works for me.  What's the problem?
> >
> > Ignore jmf.
> 
> He is trolling, ...

You know (or you don't), LibreOffice and Python is also
not working.
Finally somebody found what I was able to provocate well
~2 years ago.

jmf

PS It's a child play to repeat it (with LibreOffice
or with my interactive interpreter).

[toc] | [prev] | [next] | [standalone]

#81282

Le jeudi 20 novembre 2014 10:04:40 UTC+1, Christian Gollwitzer a écrit :
> Am 20.11.14 09:40, schrieb Chris Angelico:
> > On Thu, Nov 20, 2014 at 7:25 PM, Paul Rubin <no.email@nospam.invalid> wrote:
> >> wxjmfauth@gmail.com writes:
> >>> Today, there are simply no more valid and working
> >>> GUI toolkit running "out of the box".
> >>
> >> Tkinter still works for me.  What's the problem?
> >
> > Ignore jmf.
> 
> He is trolling, but in this point he is right, unfortunately: neither 
> Tcl nor Tk support Unicode outside the BMP. Full Unicode support is a 
> big todo item on the wishlist for Tcl 9, for Tk nobody really knows. We 
> are lacking manpower and people with specialized knowledge. Apple is a 
> moving target, they pulled the rug from under Tk's feet twice over the 
> past 10 years. Nobody knows if Tk will continue to exist on the mac if 
> Cocoa is withdrawn some day and replaced by a new and completely 
> different windowing framework. Python has largely replaced Tcl as the 
> first-choice scripting language, and that also does not help to attract 
> people working on Tcl/Tk.
> 
> 	Christian

I think you are not understanding the point very well.

Py32 and Qt derivative + plenty of dirty tricks.
(It will probably not be rendered correctly.)

Write something like this (an interactive interpreter)
in Py32 and Py33 and see what happens:

>>> print(999)
999
>>> sys.version
'3.2.5 (default, May 15 2013, 23:06:03) [MSC v.1500 32 bit (Intel)]'
>>> # note the emoji and the private use area (plane 15)
>>> a = 'abc\u00e9\u0153\u20ac\u1e9e\U0001f300\udb80\udc00z'
>>> print(a)
abc需ẞ🌀󰀀z
>>>

Note: it can be "cut/copied/pasted" with a MS product.

jmf

PS I have to recognized, I'm slowly getting tired to
find thousand and one ways to make Python crashing
or failing.

[toc] | [prev] | [next] | [standalone]

#81459

[Multipart message — attachments visible in raw view] — view raw

On Nov 21, 2014 10:09 PM, "Michael Torrie" <torriem@gmail.com> wrote:
> I can't speak for wxWidgets, but when I last looked at it years ago it
> fairly reeked of MFC-style GUI programming with event tables instead of
> a nice, flexible signal/callback interface.  Has this changed?

I recall the C++ implementation uses or used event tables, although I'm not
up on the details. The Python bindings have always used callbacks however.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.python

csiph-web