We consider a system of loadable modules, each with their own threads, each accessing all the same system command symbol. It woks if they divide into group, and each group share their won argslist, should be fine.
So, if Xchars, for example,services different argslist, their should be no interference if the windows are attached to that particular argslist. The value .args, is unchangeable once a particucular loadable starts using a new one. Through layers of subsystems, each lay still accessing the arglist from the bottom, is the standard. So, a single loadable, on its own thread can establish that same arglist with Xchars, and Xchars knows where the stated variable lies that is need, they bind. The simplicity of Xchars (strout(str,x,yz); means that ad hoc running applications can independently throw up an Xchars screen and produce output, all within the running application controlled at console.
A gra system forsnippets. Xchars remains tiny, a lower layer, a driver. All the enhanced XChar windows are themed for applications and forms; like an entire industry, like background screens. Be each enhanced xchars add functionality, string and form management and multiple widows. Never leave the font system, make is all font sized, leave the interface to five, maybe six basic calls.
Loaded modules, all sharing universal interface, all sharing the process and under control, but acting peer to peer.
No comments:
Post a Comment