Again IMGUI. Several years ago there was a chain of videos and blog posts by different authors. People were drawing two buttons and saying "see how easy it is".
In this post the author seems to go further than two buttons, but I'm skeptical. I wish there was a video showing how it works in dynamics - inputs clicked, texts entered, scrollbars scrolled, dialogs dragged around. Or source code available to build and try locally.
From the code in the post I suppose the majority of UI is dead - can not be interacted with.
I think IMGUI can only be convenient for very simple cases.
In real frameworks the lowest level is immediate mode (see WM_PAINT in WinAPI), but real UI needs quickly evolve them into the traditional RMGUI.
BTW, this thinking is my source of doubts about React.
I think you have it exactly backwards. Most ImGUI use cases are extremely complex UIs and that's where they excel.
One of the most complex apps out there, Unity, is entirely ImGUI based for the app itself and often has 1000s of controls visible. Going though the screenshots of typical ImGUI usage most of them are on the complex side.
In this post the author seems to go further than two buttons, but I'm skeptical. I wish there was a video showing how it works in dynamics - inputs clicked, texts entered, scrollbars scrolled, dialogs dragged around. Or source code available to build and try locally.
From the code in the post I suppose the majority of UI is dead - can not be interacted with.
I think IMGUI can only be convenient for very simple cases.
In real frameworks the lowest level is immediate mode (see WM_PAINT in WinAPI), but real UI needs quickly evolve them into the traditional RMGUI.
BTW, this thinking is my source of doubts about React.