smallfunction VS lqml

However, std::function which can be used for storing multiple closures can indeed heap allocated. Since this is undesirable, I use an equivalent with static fixed storage instead: https://github.com/jcelerier/smallfunction/blob/master/smallfun/include/smallfun.hpp which gives me a compile error if I try to stuff too much data in there.

and conversely from the engine to the UI thread ; Qt signals do not cut it as emitting them allocate, if only a few bytes. (Doing it naively with std::function doesn't cut it either - I use this instead to store these functions: https://github.com/jcelerier/smallfunction/blob/master/small... ; also, the audio threads feeds back those functions into the main thread after their execution so that any memory owned by the lambda ends up being freed here and not in the audio thread.)

Was wondering how practical using lqml for developing Android apps would be.

screenshot / repo / official meshtastic web site

There is lqml, which is cross-platform, including iOS.

Check out https://gitlab.com/eql/lqml and other repositories in this group.

The advantage of LQML is that you can develop your app on the desktop first (as I did with the cl-repl app), mostly without restarting anything, because QML can be reloaded at runtime. A good example to learn how this works would be this one: qml-auto-reload

Notably - 1. https://github.com/lispnik/iup/ 2. https://gitlab.com/eql/lqml 3. https://github.com/bohonghuang/cl-gtk4

In this example, there is an example call to Objective-C, which in turn is callable from Lisp.