| 2018-07-25 06:48:27 |
Momozor |
bug |
|
|
added bug |
| 2018-07-25 06:48:27 |
Momozor |
attachment added |
|
some torios programs running on yad memory consumption https://bugs.launchpad.net/bugs/1783485/+attachment/5167429/+files/torios-perf.png |
|
| 2018-07-25 06:48:58 |
Momozor |
description |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size of memory for just a tiny program.
Also, isn't it great to use a consistent widget (FLTK) for default torios applications? (eg, volume, batteri, shutdown and restart, etc) and maybe, OBI's gui too? |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size 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? |
|
| 2018-07-25 06:51:25 |
Momozor |
description |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size 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? |
https://github.com/darealshinji/fltk-dialog
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? |
|
| 2018-07-25 06:56:06 |
Momozor |
description |
https://github.com/darealshinji/fltk-dialog
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? |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size 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 using C++ (unless they are trivial to implement) will consume a lot of time, debugging and testing. |
|
| 2018-07-25 06:57:13 |
Momozor |
description |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size 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 using C++ (unless they are trivial to implement) will consume a lot of time, debugging and testing. |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size 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 using C++ & FLTK (unless they are trivial to implement) will consume a lot of time, debugging and testing.
So, why not just replace and modify the calls for yad/zenity to fltk-dialog instead? |
|
| 2018-07-25 06:57:43 |
Momozor |
description |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size 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 using C++ & FLTK (unless they are trivial to implement) will consume a lot of time, debugging and testing.
So, why not just replace and modify the calls for yad/zenity to fltk-dialog instead? |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size 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, debugging and testing.
So, why not just replace and modify the calls for yad/zenity to fltk-dialog instead? |
|
| 2018-07-25 07:02:31 |
Momozor |
description |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size 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, debugging and testing.
So, why not just replace and modify the calls for yad/zenity to fltk-dialog instead? |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size 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? |
|
| 2018-07-25 09:44:17 |
Momozor |
description |
https://github.com/darealshinji/fltk-dialog
Yad and zenity applications that depends on gtk ui (gtk+3) seemingly consumes a significant size 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? |
https://github.com/darealshinji/fltk-dialog
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? |
|
| 2018-08-15 05:21:24 |
Momozor |
bug watch added |
|
https://github.com/darealshinji/fltk-dialog/issues/1 |
|
| 2019-05-01 07:00:36 |
Momozor |
torios: status |
New |
In Progress |
|
| 2019-05-04 03:22:43 |
Momozor |
torios: milestone |
torios-1.0.0 |
torios-1.5.0 |
|
| 2019-05-06 19:26:23 |
Momozor |
torios: assignee |
Israel Dahl (israeldahl) |
Momozor (momozor4) |
|
| 2019-05-06 19:26:38 |
Momozor |
torios: assignee |
Momozor (momozor4) |
Israel Dahl (israeldahl) |
|
| 2019-05-08 02:10:44 |
Momozor |
torios: milestone |
1.5.0 |
1.5.1 |
|
| 2019-05-08 02:10:44 |
Momozor |
torios: assignee |
Israel Dahl (israeldahl) |
Momozor (momozor4) |
|
| 2019-05-08 04:25:10 |
Momozor |
nominated for series |
|
torios/torios-1.5 |
|
| 2019-05-08 04:25:10 |
Momozor |
bug task added |
|
torios/torios-1.5 |
|
