@faraco
I like this idea, but there are a few issues to consider.
1. can this do all the things we already do? Would rewriting the programs to use this justify not just rewriting them using C++?
2. tray dock icons. (the big issue here). Volume, and battery icons are handled by YAD (as well as their menus, etc...) so we need to use YAD OR write a FLTK tray dock indicator icon program.
So, I think making some simple FLTK programs to replace things would be really easy, and save on resources, but some programs probably just wont work without the complicated YAD/Zenity dialogs, unless fltk-dialog is nearly feature complete with those others...
@faraco
I like this idea, but there are a few issues to consider.
1. can this do all the things we already do? Would rewriting the programs to use this justify not just rewriting them using C++?
2. tray dock icons. (the big issue here). Volume, and battery icons are handled by YAD (as well as their menus, etc...) so we need to use YAD OR write a FLTK tray dock indicator icon program.
So, I think making some simple FLTK programs to replace things would be really easy, and save on resources, but some programs probably just wont work without the complicated YAD/Zenity dialogs, unless fltk-dialog is nearly feature complete with those others...