It is not meant to be a production API. I have started stdui as a personal project and wish it to stay personal because I am ( as I said ) learning and experimenting UI from scratch and is certainly not of any "professional"interests.
As experimentation, various engines/designs can be totally out of the track, or otherwize, some parts/aspects be good ideas that can be re-thought, used, improved, scrapped, etc...
The ways I understand the various aspects of a User-Interface, the designs and the C++ programming language will change and evolve during the development of this project.
Right now I describe my related skills as old-time beginner. I did make various (text) UI in the past ( old days of MS-DOS 6.22 and Borland Turbo C++ before M$-Window 95. ).
Since Linux/GNU is relatively new for me, there are several programming aspects that I not even understand enough, such as
The current API structure contains several design errors and are about to be re-written if not already in the way to be corrected.
One such error is that actually, stdui: window class doesn't make distinction between embedded widgets and usual/visual Window object classes.
That's it, distinctions are made in the (window's) style flags of the window object. That really complicate the area of updates/refresh details.
The solution to that design error is really to replace the actual stdwindow class with its actual behaviours and features by a stdwidget class object that will serves as the base class of the other visual objects in the API. Making the assumption that a "stdwindow" is actually a TOPLEVEL widget that contains and features behaviours like a real window in the (actual, standard) user-interface world