xchars renders fonts, a font iss eight bits, or an index into one of 256 patterns. Fonts typically occupy a 150 pixel rectangle. So, making chart fonts works best in a multi-processing rectangle structure, the rectangle system keeps data confined. Have the chart maker do the math, plotting and charting fonts re around, somewhere. The user is trying to keep the separate processes from interacting in controlled manners, rectangles is the user model.
Nothing prevents a snippet from using the binary interface to xcbars and taking on the whole window as graphics display. Likely would be a standard if we kept driving the rendering technology for xchrs, so it keeps up in speed. If font sizes are flexible, and font sets already loaded, then there is a smooth transition to vector graphics,, and real bitmaps. Font patterns should be an easy render, everything is fixed size increments according to current font. The math on the other side is not too bad. It is the scalability of fonts, they can scale up and describe parts of a creature.
But the NoteBook is a classic use case for the xchars concept. Here is a screen shot of a simple Jupyter notebook. They do much more sophisticated stuff, already have qt_lite on their bus. But given the lightweight intentions of the default configurations, we aim for this simple result.
Here is looks like four rectangles going. Everything here is character based, with some border overlay, simple stuff. Getting qt_lite, or SQL_Lite in there is simple stuff, but we focus on the default, what you get with no dependencies, you got basic console loop, with Default, io manager, and xchars. Why not adopt jupyter? Why not? Console loop and all that will drop into the lowest of layers and find a niche, manage the enterprise args list. Remain focused on snippets, threads, speed, shared memory, interactions. But with a focus on the adaptability of xchars as a rendering interface, leading to wayland and high speed font rendering, xchars can hold top position, easily. Stay out of jupyters way, but share as much as possible.

No comments:
Post a Comment