(core): harmonize AppConfigManager/AppManager
Description
AppConfigManager
is used to manage a XML application, while AppManager
manages C++ applications. They share a very similar behaviour, but they do not share code.
Outcomes
Ease code maintenance. Less code, fewer bugs.
Proposal
- If we think it is worth keeping C++ applications, sharing code would be desirable. To help do this, we should change the main difference between the two, which is the fact that unstarted services (with deferred data) are not instantiated in
AppConfigManager
, while they are inAppManager
. Always creating services inAppConfigManager
would be the best solution, and could really help to remove the duplicated configuration/registration of data. We could also rely on thehasRequiredObjects()
function instead of the implicit similar mechanism coded inAppConfigManager::addObjects()
. - Remove AppManager and all associated tutorials
Functional specifications
Finally, I propose to remove AppManager and all associated tutorials. This approach was not really relevant. This implies removing most Qml samples. We keep only the basics, necessary to launch widgets written in Qml.
Technical specifications
Remove AppManager
files, tests and tutorials.