Tutorial Requests

[OogieM]

Classes work best with tkinter, one reason is the ample use of forward references, for example a button press event,
since all methods become available when the class is instantiated, forward referencing is never a problem.

Let's take that as an example. If I have a class that has several tkinter widgets in a specific frame. One of them is a combo box that is disabled and empty except for a placeholder. In another frame I have a button with an onclick event bound to it. When that button is clicked the what I want to have happen is that a database query will be run with parameters from the second frame (where the button I clicked is located) and one of those will update the combobox in the first frame with the applicable choices. In another case I have to read the state of a bunch of checkboxes and based on them add SELECT clauses in a query that will diusplay only certain fields. What I can't find are tutorials on how to implement the actions of read the contents of the first frame and update some of the items based on results in the second frame.

It's the lack of specific detailed examples that I wish were available.

Finally, I'll mention that although it's possible to write large GUI applications with tkinter, it's difficult at best.
I have done it, but it's many times easier with wxpython which is much more robust. There's also Qt (Qt5 being latest version).

I eliminated Qt due to licensing issues. It won't work in my application.

Most of the stuff I had found on wxpython indicated it was not particularly robust on Macintosh computers. Since the majority of the users are on a Mac that is a big issue. The app is supposed to work on all 3 major platforms, Mac, Linux and Windows but the focus is Mac first, Linux second and if it works on Windows great. If I am mistaken I'd love some references that have good examples. A lot of what was out on the web that I found initially said it wouldn't work with Python 3.7 but I've since found out that is wrong.

I'm not sure what is considered a large GUI application. I have what I think are fairly simple requirements but maybe I'm wrong about that have several top level windows with various input and output widgets on them. In most cases a single window is self contained, I don't usually need to pass data to another window. There are a coouple of cases where that happens. While the nuts and bolts of what is displayed vary the basic functions do not. User selects a set of display items, and a set of limiting criteria. A query into the database is forumulated from those inputs and the result is displayed in a frame on the window. Further selection of individual records and then applying actions that will edit a single or group of them or writing reports are the other major functions.