Replace yad and zenity dialog with fltk-dialog
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
ToriOS | Status tracked in Torios-1.5 | |||||
Torios-1.5 |
In Progress
|
Wishlist
|
Unassigned |
Bug Description
https:/
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant amount of memory for just a tiny program.
Also, isn't it great to use a consistent set of widgets (FLTK) for default torios applications? (eg, volume, batteri, shutdown and restart, etc) and maybe, OBI's gui too?
Yes, we can use C++ & FLTK but there are many existing shell applications being written already by israeldahl and niowiklund.
I believe to rewrite them all over again into C++ & FLTK (unless they are trivial to implement) will consume a lot of time for debugging and testing.
So, why not just replace and modify the calls for yad/zenity to fltk-dialog instead?
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in torios: | |
status: | New → In Progress |
Changed in torios: | |
milestone: | torios-1.0.0 → torios-1.5.0 |
Changed in torios: | |
assignee: | Israel Dahl (israeldahl) → Momozor (momozor4) |
assignee: | Momozor (momozor4) → Israel Dahl (israeldahl) |
Changed in torios: | |
assignee: | Israel Dahl (israeldahl) → Momozor (momozor4) |
milestone: | 1.5.0 → 1.5.1 |
@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...