Skia VS imgui

Not specially something that you cannot do without WASM but at $WORK we are using a WASM build of Skia [0] to render canvas from nodejs.

Why use WASM ? Because we wanted to stay close to our stack (ie. calling wasm from nodejs). Do it work ? Yes, memory consumption is quite heavy though (each WASM module have its own heap that can quickly grow).

However we are looking to directly use Skia now and avoid the overhead of WASM so i think its a nice solution in the beginning but you might want to ditch it later on.

[0]: https://github.com/google/skia/tree/main/modules/canvaskit

I use SkVx from Skia. It uses compilers' vector extensions and few platform-specific intrinsics. If no vector extension available (e.g. msvc), a scalar implementation is provided in the hope that compiler can vectorize it.

Regarding compiling to JS, you can compile dart to JS however when running Flutter on mobile platforms such as iOS or Android, you're not compiling to JS but instead you're using Dart to draw widgets on the screen via Flutter engine which uses a cross-platform graphics engine under the hood called Skia. If you're running on web on the other hand, your dart code would compile to vector graphics rendered within a canvas element in pure HTML.

It built on a render framework named skia, JetBrains create a kotlin mapping which named skiko for it.

Flutter applications are written in the Dart programming language, and can connect to platform languages such as Java, Kotlin, Swift, and Objective-C. Also, thanks to ffi support, it is possible to interact with the C code directly . Flutter itself is built with C, C++, Dart, and Skia (a 2D rendering engine).

Fleet does not use Compose, but it does use Skiko[1], which also provides binding for Skia[2] (the native graphics library also used by Chrome & Flutter).

The main difference between the libraries is that Skija provides Java/JVM bindings for Skia, whereas Skiko provides Kotlin bindings for Kotlin/JVM, Kotlin/JS, and Kotlin/Native targets. Of course Skiko's Kotlin/JVM bindings can be used with other JVM languages, not just with Kotlin.

[1] https://github.com/JetBrains/skiko

[2] https://skia.org/

RN Skia: https://github.com/Shopify/react-native-skia Skia itself: https://skia.org/

Yeahp, it renders the controls itself using skiasharp, which I believe uses skia

If you want CPU rendering perhaps tiny-skia meets your needs? Also proper Skia is generally the Cairo alternative, though I dunno that its any easier to use or compile than Cairo is. Alternatively you could try Raqote or Piet.

First step: Read the documentation. I see at the bottom of the github page that there's a link, so I go there: https://skia.org/

Currently, I have narrowed potential libraries to: 1. Flutter 2. FLTK 3. Relm (GTK) 4. iced 5. Slint 6. Imgui, Imgui-rs 7. and gtk-rs

Imgui, Imgui-rs

Dear ImGui easy to use and understand immediate mode is simple to understand and fits games with a render loop Small file size Con: Doesn't look like your native OS widgets

- X Toolkit Intrinsics Reference Manual

However they have very little to do with how modern operating systems (Windows, MacOS) deal with that stuff.

As for toys, I'd recommend reading about Dear ImGui [1]. It handles everything you mentioned while being self-contained so you can see how everything works from top to bottom. Many talks and articles have been written about it though I can't vouch for any of them.

1. https://github.com/ocornut/imgui/wiki

Check out these: https://github.com/ocornut/imgui https://github.com/mikke89/RmlUi

ImGUI (https://github.com/ocornut/imgui) probably as simple as it can get

One simple, rather unimportant GUI library is this one, and even they claim a pretty long user list

Dear ImGui and SFGUI are options.

Raylib was created primarily for game development. If all you need is a minimal graphics library for drawing ui, then I would check out Nuklear or IMGUI Raylib will not help all that much with writing code to interface with the arduino and calculate the map.