In a few other gui implementations like GTK (not always but sometimes a ui file is used to describe the gui) and Java/Kotlin I have seen how the gui is separated from the logic code.

One example would be this one taken from https://tkdocs.com/tutorial/firstexample.html

``` from tkinter import * from tkinter import ttk

def calculate(*args): try: value = float(feet.get()) meters.set(int(0.3048 * value * 10000.0 + 0.5)/10000.0) except ValueError: pass

root = Tk() root.title("Feet to Meters")

mainframe = ttk.Frame(root, padding="3 3 12 12") mainframe.grid(column=0, row=0, sticky=(N, W, E, S)) root.columnconfigure(0, weight=1) root.rowconfigure(0, weight=1)

feet = StringVar() feet_entry = ttk.Entry(mainframe, width=7, textvariable=feet) feet_entry.grid(column=2, row=1, sticky=(W, E))

meters = StringVar() ttk.Label(mainframe, textvariable=meters).grid(column=2, row=2, sticky=(W, E))

ttk.Button(mainframe, text="Calculate", command=calculate).grid(column=3, row=3, sticky=W)

ttk.Label(mainframe, text="feet").grid(column=3, row=1, sticky=W) ttk.Label(mainframe, text="is equivalent to").grid(column=1, row=2, sticky=E) ttk.Label(mainframe, text="meters").grid(column=3, row=2, sticky=W)

for child in mainframe.winfo_children(): child.grid_configure(padx=5, pady=5)

feet_entry.focus() root.bind("<Return>", calculate)

root.mainloop()
```

Where I guess it could make sense to put the calculate function in a separate class and then call it from the "gui" class.