vedderb
Package based apps should show up in list of apps and not get enabled automatically
If we want package based apps to feel like a true upgrade compared to 5.3, I'd like to see some tighter integration.
When loading a custom package, we should have this package show up in the list of apps, or at least we should be able to declare a package as an app, and then it needs to show up in the list. A package that declares itself as an app should be added to the list of apps (with a name defined in the package, not just Custom0), and then the user still needs to manually select that app as the active app (they may not have finished motor config yet)
Also, when I need to redo the motor wizard or hall sensor detection, how can I safely do that when I'm using a Lisp balance package? Do I need to uninstall it and then switch to the UART app? I myself don't even know (since there's no documentation that I know of) - Being able to switch to the UART app and be certain that my package app isn't going to interfere will make this much easier.
If you don't see the upgrade you are completely and utterly missing the point. The main point is that you can maintain the package independent of messing with the firmware so that users don't have to be on the beta with ever changing configs and vesc tool versions or wait for the next release in several months to a year. It also solves the problem that there simple isn't space to have for example the balance app and the float app at once in the firmware (or other apps for that matter) without having 100 different versions of vesc tool and firmware binaries flying around.
