I’m getting whiplash going from Racket’s fantastic GUI library to Tkinter

Python needs a GUI library that is Actually Good because this is so painful to use T_T

I give up on Tkinter (it’s not worth learning something that has such bad documentation) but I’m going to try wxPython next. if that doesn’t work I might just have to make this clicker game in something gross like TypeScript

@kasdeya I had some success with Kivy in the past, this was some years back though.

@kasdeya tkinter is kinda bad but also pretty learnable IMO
i ended up using FLTK (in C++ written like plain C but run in a C++ compiler) for a lot of stuff later on. maybe there are python bindings for FLTK, It's ptetty simple and nice overall. Although I dod patch the fltk sources for a couple things, it was pretty easy to do, statically linkable, and not something i was discpuraged from doing when i asked on the IRC channel

tbh I think a whole lot of documentation issues could be solved by just letting people comment on different documentation pages. because then as I’m trying to figure Tkinter stuff out I can leave comments explaining what I’ve learned which will help the documentation be more complete, and save others from having to do the trial-and-error that I’m doing

@wyatt ooh I’ve never heard of FLTK! it looks like there are incomplete bindings for Python so that’s pretty cool tbh. and I like how FLTK looks as well - it seems nice and simple and fast

also that’s interesting that you essentially wrote C for a C++ compiler. I don’t know too much about either of those languages and I’m curious why you did that

@benrob0329 I’ve been thinking about trying Kivy as well! in fact I might try Kivy first and then wxPython after that - since Kivy seems like it has good documentation and even a nice tutorial. and it doesn’t seem too complex either - at least not at first glance. thanks for the recommendation 💙

@kasdeya the FLTK library, which is C++, is nonetheless written in such a way that I can write a program that uses it that doesn't use fancy C++ stuff like namespaces, just essentially "the C parts" in my own code.
And I don't like reading or writing most C++ unless it's used in a very constrained way as a slightly fancier C

@wyatt ohh that makes sense! so it sounds like you essentially had to use C++ if you wanted to use FLTK, but you didn’t have to use all of its fancy features - and I’m glad! it’s pretty cool that FLTK’s API is written that way

@kasdeya Most C code is also valid C++ so it's nice when libraries take advantage of that