Sep-06-2020, 01:46 PM
I'd like to see a tutorial on how to apply OOP and classes to managing GUI applications using tkinter.
Classes and objects make sense to me in terms of the standard examples (a Car class, etc.) Where I lose the connection is trying to make a frame in a tkinter window a class, which several tutorials suggest, and then getting user inputs in that frame and and passing that data to another frame in the same window where it will be used to calculate or retrieve information that will then be displayed in yet another frame.
Simple things like how do you specify the location of a frame when it's a class (I'm using grid placement for all my tkinter stuff) and how do you create it? How do you actually call the various methods that you might create that read the contents or user input and then send it on to the next class for use? I'm not planning on having 2 copies of any specific frame class in the same window but I may have copies of the same frame class in multiple top level windows.
Classes were what I was told to use because in many cases the code to produce the contents of a single frame is the same across several windows.
I'm coming from Java on Android and there a single window is an activity and all the UI pieces (buttons, user inputs, outpur fields, etc.) are available to any code within that window. They all can operate independently.
Classes and objects make sense to me in terms of the standard examples (a Car class, etc.) Where I lose the connection is trying to make a frame in a tkinter window a class, which several tutorials suggest, and then getting user inputs in that frame and and passing that data to another frame in the same window where it will be used to calculate or retrieve information that will then be displayed in yet another frame.
Simple things like how do you specify the location of a frame when it's a class (I'm using grid placement for all my tkinter stuff) and how do you create it? How do you actually call the various methods that you might create that read the contents or user input and then send it on to the next class for use? I'm not planning on having 2 copies of any specific frame class in the same window but I may have copies of the same frame class in multiple top level windows.
Classes were what I was told to use because in many cases the code to produce the contents of a single frame is the same across several windows.
I'm coming from Java on Android and there a single window is an activity and all the UI pieces (buttons, user inputs, outpur fields, etc.) are available to any code within that window. They all can operate independently.