Jackson Hu

I also have some ideas about this. I think LVGL can fit in Wasm3 perfectly and some (but maybe not all) functions bindings can be generated by LVGL's official tool....

> Basically, we can either 1. modify this Python script, to make it generate Wasm3 binding instead of MicroPython binding, or 2. make use of the JSON output from this...

@kisvegabor I'm thinking to implement a simple Nodejs tool with some template engines like [Mustache.js](https://github.com/janl/mustache.js), consume LVGL's JSON and output a generic C binding. I'll probably try doing it next...

> I think the next step would be to create a minimal PoC, some "hello world" app with minimal API dependency. No need to auto-generate anything yet. There you go:...

> Yeah, I mean create lightweight WebGPU ES which similar to OpenGL ES in term of adoption @MaxGraey This is a good idea, but I doubt it may not work...

> LVGL is written in C so it has no OO API, but it mimics it to the extent the language allows. E.g. Instead of `btn1.set_width(20)` we have `lv_obj_set_width(btn1, 20)`....

> @kisvegabor I envision something like this. Green boxes could be auto-generated: > >  > > We already have examples of "apps" in multiple languages: https://github.com/wasm3/wasm3-arduino/tree/main/examples_pio/Wasm_Advanced/wasm_apps > They use...

Here's a quick and dirty PoC script that generates C function signatures based on LVGL MicroPython binding generator's JSON manifest: https://github.com/huming2207/lvgl-wasm3-bindgen Run `npm i` and then `npm run dev` and...

> The tool will become more useful if we can make it generate not only LVGL binding for wasm3 but other C library for other high level language(much like IDL...

> I recommend using TOML instead of JSON as the manifest I think both of them are fine. It's mainly for the machine to read it, not humans anyway. For...