Python wrapper for milligui

[willpatera]

Hi Mikko,

Really appreciate the work you are doing with nanovg and milligui!

We're currently using ATB in our project and have been looking to replace it for a while now -- ideally with a lightweight (and contemporary) GUI -- enter milligui. We were thinking of contributing to milligui by writing python bindings, but wanted to get in touch with you first to learn more about how you plan to move forward.

In example.c the GUI elements are created within the main loop (imgui style). But in example2.c it seems that you have created a data structure to save the state of the GUI.

For my own purposes, I would prefer a state based GUI (along the lines of example2.c). Are you leaning towards one?

[memononen]

Hi, The API is still very much in flux. My plan is to make it imgui style, thus, quite stateless, but I'm trying to test a different approaches.

Can you elaborate a bit what kind of requirements you have for your API? Maybe also why you prefer state based GUI? Is there a project out there (regardless of language or platform) which makes GUI programming fun? I'm very interested to learn how people approach writing UI.

[willpatera]

Thanks for the response and apologies for the delayed reply. The topic of state based GUI vs imgui seems to be a very heated debate -- and I don't pretend to have any dogmatic opinion in that arena. However, my state based comment comes from the fact that I don't have much experience working with imgui's.

I don't really know of any project that makes GUI programming 'fun' per se -- it'd be great to hear your thoughts on this.