pyNuklear

For more context, immediate mode is much closer to the type of declarative UI popularized by libraries like React. The invariant is that what is displayed on screen is always a pure function of some state variable(s), and on any input/event, instead of needing to "reach into" some retained object that represents a certain piece of text in a certain pane in a certain window, you just change those state variables and re-render the entire UI from scratch. Sounds expensive, but for a 2D UI on hardware that's designed to do far more complicated things at 60FPS, it's far from the bottleneck. For instance, https://github.com/billsix/pyNuklear/blob/master/demo/overvi... (this function is called repeatedly on each frame) is not significantly different from the example at https://reactjs.org/tutorial/tutorial.html#what-is-react ... but it is very

Retained-mode GUIs like Qt , wxWidgets, gtk, etc aren't intuitive. Try an immediate mode GUI, like my python bindings to nuklear https://github.com/billsix/pyNuklear

If your looking for a nice gui framework for python, check out my pyNuklear! https://github.com/billsix/pyNuklear

For python fans, I've been working on pyNuklear https://github.com/billsix/pyNuklear

Came across this yesterday: Nuklear This is a minimal state immediate mode graphical user interface toolkit written in ANSI C and licensed under public domain. https://github.com/vurtun/nuklear https://github.com/billsix/pyNuklear

https://github.com/billsix/pyNuklear if nuklear.button_label(title="Button"): print("Button pressed!")

Immediate mode graphical user interfaces have changed the way I look at GUI programming for the better. Here are my bindings to python for the nuklear framework. https://github.com/billsix/pyNuklear