My simple Ncurses

50 lines of code, three APIs.  init_screen, int_to_str, put_screen.

The rule is, do not put any \n or \0 in the screen buffer, it is initialized to space. Printable, single char width only.

 I can do all the character graphics I want, someone else can make it official and deal with the code bloat of  modern GUIs.  I can make tables and trees. I never have to screw with utilities that may or may not put in non printables while doing IO..  Best of all, easy to deploy using the old CutnPaste method for software configuration.

WASM fixes a lot of this graphics problem.  WASM can deploy high speed graphics buffer routines, we will get much better browser applications. For researches then graphics in the browser is almost automatic, no hundreds of lines and thousands of APIs days to set up. In the lab, WASM will allow complete control of the browser screen with a simple set of draw utilities, almost like SDL for browsers.

Using my mini_curses with join.

Take the CONSOLE attachment, add the 50 lines of code and implement step and skip. Define key size for skip, the way MEM does it, but simpler. Output the screen buffer on Done. You have a database accessible by XY coordinates, but managed as a step and skip graph. Limited to printable key alphanum char key values, fix size text windows.