BlissLauncher V2
This issue is intended to improve the overall structure of BlissLauncher. Currently, BlissLauncher shows unexpected behavior and crash due to error-prone code.
This refactoring and migration is aimed to fix the following issues ->
-
#653 (closed) -
#792 (closed) -
#793 (closed) -
#794 (closed) -
#795 (closed) -
#800 (closed) -
#801 (closed) -
#802 (closed) -
e/backlog#805 -
#806 (closed) -
#838 (closed) -
#832 (closed) -
#829 (closed) -
#827 (closed) -
#825 (closed) -
#811 (closed) -
#814 (closed)
This refactoring process is also intended to make Launcher more reactive, lightweight, and low memory usage. The code will be more organized, well structured and maintainable. This issue targets BlissLauncher V2.0
Edited by Arnau Vàzquez