How does xchars handle the browser function?

How would xchars mimic the Jupyter browser based rectangle system?
It doesn't, bu xchars lets a browser function connect to one of its rectangle using a binding interface.  So one particular window can be web browser and another running QT_Charts. So the encapsulation is reversed, or more precisely, the xchars system, at the command line level, is low level, it is something that browsers build intelligence onto.  But the symbol table, the universal bus all make the lower level of rectangle available universally, as long as you can pick a unique name for your rectangle.

The new  systems will adopt this new decomposed approach, it enables a whole host of configurable applications if we can get plain text access to the lower level.  Jupyter will do a simple switch out from xwindows to an xcb/cairo style rendering system, and lower level rectangle access is automatic.  Any implementation of xchars that additionally exposes the xcb interface is a jupyter candidate at run time configuration.

It mastters not if the code is mine or hers, the semantics dictate a simple solution.  There is a rectangle, it has a name, it has an optional size, it is one you make.  There are like, three different, basically the same, combinations of those variables, there is no need to complicate the interface, add typeface explosion, run 20,000 lines of ncurses, or call grandma.  Just ask, using the common form with plain text, choose your favorite unique name, acquire bunches of them.

What?

browser ./startpage newrect conn myrect;

Browser has top name space, how it unfolds generates the steps needed to consume following arguments. All is plain text. you see in the examples a name space grammar emerge, rules and order to maintain unique names at all point of argument consumption, going left to right. The immediate name space terminates at semi-colon, but import ed name spaces have persistence.  Names must be unique command line to command line regardless so user can carry key values across his interactions, local persistence.

Note my file indicator ./  ;  We can remove that with a file snippet having symbol table front end. Hundred lines of code, well worth it as files can have ad hoc local names with hardly any cost. I might change my m,ind about keeping that double operator, but then it may be one of those typeface explosions that prove the rule, it is only there because of long standing use among everyone since the dawn of computer disks.

A simple, programmable name space function, identical; enterprise wide. It is where we were all headed, as the geeks will assure you. Go,go,go.