kettle11 / kui Goto Github PK

What's the goal for this UI lib regarding architecture? Will this be immediate mode UI lib (e.g. https://github.com/Immediate-Mode-UI/ ) or rather retained mode UI lib?

How would kui solve the example described in vlang/ui#7 (comment) and clarification?

There is no established terminology for this AFAIK, so I call it live variables or it can be viewed as reliable pub-sub mechanism or as reactors or reactivity or as "streaming data API" etc. The point is to express with the lowest possible number of SLOC that two or more distinct widget instances (each of different kind of widget and in a completely different unrelated part of the app) should get the same input event instance (kbd, mouse, IPC, ... - e.g. significant layout change as linked above) and if the widget is not "read only" (e.g. label is read only, but a button with picture/label is both read & write), then the widget instance shall also at the same time have the capability to create any number of new event instances of any kind and anyone interested in this event (i.e. "subscribed") must guaranteed receive it. This everything with defaults so well handled that most common use cases (let's define this to be equivalent to 7GUIs) shall have the very minimum of SLOC (of Rust and YAML) possible.

Is one of the goals of this library to be web compatible? I mean, can we compile it to JS (or WASM) and make it work efficiently (in terms of speed and power consumption) in browsers of modestly modern mobile devices (say those having Android 9 or iOS 13)?

I think it'd be good to add this cool UI lib to 7GUIs (ideally including also additional proposals) to ease understanding of its usage for newcomers as well as to compare its capabilities and approaches with other UI libs side by side in a fair comparison.

It'd also partially pinpoint whether layouting and "live" capabilities are well enough architectured or whether there are some sharp edges.

Please see vlang/ui#19 .