On 03/04/2023 02.45, Michael Torrie wrote:
On 4/2/23 05:09, Dietmar Schwertberger wrote:
I also did evaluate all the GUI builder from time to time between
2000 and 2016 to find one that I could recommend to colleagues,
but could not find one. Then I started contributing to wxGlade
and I can
On 2023-04-02, Michael Torrie wrote:
> On 4/2/23 05:09, Dietmar Schwertberger wrote:
>> I also did evaluate all the GUI builder from time to time between
>> 2000 and 2016 to find one that I could recommend to colleagues,
>> but could not find one. Then I started contributing to wxGlade
>> and I
Hi, Dietmer,
On Sun, Apr 2, 2023 at 1:14 PM Dietmar Schwertberger
wrote:
>
> On 02.04.2023 18:26, Michael Torrie wrote:
> > Been a long time. I was initially turned off by the event handling
> > system of wx compared to the signals and slots of Gtk and Qt.
> When starting with Python GUIs in
On 02.04.2023 18:26, Michael Torrie wrote:
Been a long time. I was initially turned off by the event handling
system of wx compared to the signals and slots of Gtk and Qt.
When starting with Python GUIs in 1999, I evaluated both.
Qt event handling had an advantage for C++ where the wxWidgets
On 02.04.2023 18:20, Michael Torrie wrote:
Well the thing is you don't need to generate Python code at all. Qt
provides a UI loader class that loads the UI file at run time, builds
the objects in memory, and connects all your signals for you.
I know, but having to load the .ui file is
On 2023-04-02 9:09 a.m., Dietmar Schwertberger wrote:
>> I've tried wxGlade but never could get into it, or wxWidgets in general.
>
> Which version? Up to 0.7.2 I agree.
Been a long time. I was initially turned off by the event handling
system of wx compared to the signals and slots of Gtk and
On 2023-04-02 9:09 a.m., Dietmar Schwertberger wrote:
> That's what I hated with Qt Designer: it does not output Python code
> but a .ui file.
> This was the point where I could not recommend it to anyone.
Well the thing is you don't need to generate Python code at all. Qt
provides a UI loader
On 02.04.2023 16:45, Michael Torrie wrote:
But any modern GUI toolkit has sizers and layout managers. If you're
manually placing elements you cannot deal with HiDPI or changing window
sizes. Rearranging happens automatically when using sizers and layout
managers.
I did not talk about pixel
On 4/1/23 09:37, Eryk Sun wrote:
> Here are a few of the GUI toolkit libraries in common use:
>
> * tkinter (Tk)
> * PyQt (Qt)
> * PySide (Qt)
> * wxPython (wxWidgets)
> * PyGObject (GTK)
>
> tkinter is included in Python's standard library.
Another good one is Kivy.
On 4/2/23 05:09, Dietmar Schwertberger wrote:
> I also did evaluate all the GUI builder from time to time between
> 2000 and 2016 to find one that I could recommend to colleagues,
> but could not find one. Then I started contributing to wxGlade
> and I can say that since a few years it's as easy
On 02.04.2023 01:13, Alan Gauld wrote:
I did a deep dive examination of GUI builders back around
v2.6 and came away less than enthused. Things may have
improved since then but I've seen no real evidence of
that.
I also did evaluate all the GUI builder from time to time between
2000 and 2016 to
> The real time consuming stuff in building GUIs is getting
> the basic design right and keeping all the controls,
> keyboard bindings and menus in sync. State management
> in other words.
And cominmg up with sensible design choices _at all_.
> I did a deep dive examination of GUI builders back
12 matches
Mail list logo
