1. You got a point and for the long term, I also rather them being written in C++ for low resource consumption and execution speed. Anyway, opening up the opportunity for people to contribute desktop application code in Bash (not everyone know C++, and I certainly don't other than the very basics) while still using the same GUI toolkit (FLTK) might not be a bad idea either and IMHO useful for quickly prototyping simple GUIs in your shell without firing the FLUID designer and a code editor.
@israeldahl
Hi again.
1. You got a point and for the long term, I also rather them being written in C++ for low resource consumption and execution speed. Anyway, opening up the opportunity for people to contribute desktop application code in Bash (not everyone know C++, and I certainly don't other than the very basics) while still using the same GUI toolkit (FLTK) might not be a bad idea either and IMHO useful for quickly prototyping simple GUIs in your shell without firing the FLUID designer and a code editor.
2. I've discussed a bit with the maintainer of fltk-dialog. He added yad --notification feature to the program. https:/ /github. com/darealshinj i/fltk- dialog/ issues/ 1#issuecomment- 412917503. I've tried on my local computer and it works well (and successfully imitates yad --notification fundamental).